[Mono-bugs] [Bug 364430] ODBC: Command fails to use a UNICODE string parameter

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=364430

User mjscod at gmx.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=364430#c4


Mark Junker <mjscod at gmx.de> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
 Attachment #197662|0                                               |1
        is obsolete|                                                |




--- Comment #4 from Mark Junker <mjscod at gmx.de>  2008-02-28 07:43:45 MST ---
Created an attachment (id=197683)
 --> (https://bugzilla.novell.com/attachment.cgi?id=197683)
Modified test source to make it run on Mono 1.2.6

I tried your source but I made several changes:
1. Using NULL as parameter value doesn't work on Mono 1.2.6
2. Use using() to ensure a closed connection (to ensure closed connection on
error)
3. Show error message if required (to find reason for change #1)
4. Pause at end (for testing from inside VS2003
5. Use conditional compilation for read/write
6. Writing the character codes (Windows console cannot show all characters and
therefore shows \u0444 as "?")

This are my test cases:

Output when inserting with .NET 1.1 and reading with .NET 1.1:
0061 a
0444 ?
0062 b
0438 ?
0063 c
0441 ?
0064 d
0432 ?
0065 e
0443 ?
0066 f
0430 ?
str = a?b?c?d?e?f?

Output when inserting with .NET 1.1 and reading with Mono 1.2.6:
1A61 ?
1A62 ?
1A63 ?
1A64 ?
1A65 ?
1A66 ?
str = ??????

Output when inserting with Mono 1.2.6 and reading with .NET 1.1:
0061 a
003F ?
0062 b
003F ?
0063 c
003F ?
0064 d
003F ?
0065 e
003F ?
0066 f
003F ?
str = a?b?c?d?e?f?

Output when inserting with Mono 1.2.6 and reading with Mono 1.2.6:
3F61 ?
3F62 ?
3F63 ?
3F64 ?
3F65 ?
3F66 ?
str = ??????

Sorry, I cannot test with trunk because I don't have the required build tools.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.