Model Search. Truncated text if value is over 255

[novikovigor]

Hello again.
There is another problem.
In model search I get notes from t_attribute and t_attributetag by SQL. Then I copy result set (select all => copy selected to clipboard) and paste it into text editor (then I open it as CSV).
But I have a problem: if text value in fields is too big it is truncated. How can I get notes from t_attribute and t_attributetag without truncating?

I find out if in database cell's value is over 255, in result set it is truncated.

[qwerty]

Report a bug.

Consider writing a script to achieve correct results.

q.

[Geert Bellekens]

If I'm not mistaken EADocx also exports data in excel.
You could try that.

Geert

[novikovigor]

I know, Geert, and I did.
But now I must organize export by SQL, it's not my decision.

[Geert Bellekens]

In that case I would write a script/addin to export the data you need.
It's really not that difficult to write to an excel file.

Just create a two dimensional array containing the data you need (which you can find using Repository.SQLQuery) and the pass that array to an operation such as:

Code: [Select]

       /// <summary>
        /// write the contents to the excel sheet starting at the given row
        /// </summary>
        /// <param name="contents">the context to write</param>
        /// <param name="beginrow">the row to start from</param>
        public void write(object[,] contents, int beginrow)
        {
            //get the exact range where the contents should be placed
            Range targetRange = sheet.get_Range(sheet.Cells[beginrow, 1], sheet.Cells[contents.GetUpperBound(0)+1 + beginrow-1, contents.GetUpperBound(1)+1]);
            targetRange.Value2 = contents;
        }
This is super fast.

Geert

[novikovigor]

Thank you, Geert, for your advice! I read articles in your blog, but all the same it would not be simple (time is runnung out).
I decide to resolve problem next way...
Using mid('string', i+255, 255) I store left-substrings into 10 different columns (it will be with reserve), then write a simple parser on java (my language), that merges in CSV these columns in one.
It will be the fastest way to resolve our problem.

Nevertheless, thanks to everybody!