Post reply

QA and ASCII 1

  • November 13, 2003 at 7:15 am

    #84737

    We encountered what appears to be a bug in ISQLW (version 2000.80.382.0) . Using Google I found one other mention of it. I am wondering if anyone else encountered it.

    When querying an encrypted field that includes an embedded ASCII 1 (SOH), when the results are to grids, the output stops before that character.

    When a second field is specified after the encrypted one, the output of the second field contains the remaining characters from the first encrypted field, and the second field's actual contents are not displayed.

    When * is specified, the remaining characters from the encrypted field appear in the next field, and all other field output is shifted right one field, and the contents of the last field are not displayed.

    This behavior isn't exhibited when results are to text, or with other query tools, like EM.

  • November 17, 2003 at 12:00 pm

    This was removed by the editor as SPAM

  • November 17, 2003 at 12:49 pm

    #482292

    Looks like ISQLW parses the results and uses Char(1) as some kind of delimeter. I've seen this before, but as you say, this is only in "Grid" mode, not really a representation of the actual data.

    Just for kicks, I executed the following:

    select 'Data for Col 1' + char(1) + 'Col 1 cont.' as Col1

    select 'Data for Col 1' + char(1) + 'Col 1 cont.' as Col1, 'Col 2 data' as Col2

    select replace('Data for Col 1' + char(1) + 'Col 1 cont.', char(1), '[Char(1)]') as Col1, 'Col 2 data' as Col2



    Once you understand the BITs, all the pieces come together

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply