|
[
Permalink
| « Hide
]
Kovalenko Dmitry added a comment - 15/Oct/08 08:21 AM
If is it need, I can sent the private tests (for Windows 32/64) with demonstration of this problems.
> Insert [connection ctype: UNICODE_FSS] large string with 1048576 UTF8 chars from CP943C charset
What you mean? If your blob is being created as UNICODE_FSS but you put CP943 bytes, it's obviously that you will have problems. If that is not the case, please sent the test case. Hi
The problems still occur for single-byte ICU-charsets - TIS620 Sample test: blob.002.unicode.TBL_CS__TIS620.COL_BLOB.ins_UNICODE_FSS.sel_TIS620.len_32767.chars_TIS620.bind__wstr And, after correction - for all lengths of multi-byte ICU-charset - CP943C Sample tests: blob.002.unicode.TBL_CS__CP943C.COL_BLOB.ins_CP943C.sel_CP943C.len_*.chars_CP943C.bind__wstr Ofcourse, may this is other problems, and they will be decided in separate changes See also our old BUG-1596 :-) Thanks Does your test run in loop or it have too many blob.002* tests?
I tried run blob.002* and it never ends... I have the great workstation + patience :-)
Re-opened upon request of the bug reporter. He insists the problem still exists.
Then I expect from Mr. Kovalenko sources for his test as well as a way to compile and debug it.
I can do nothing looking at the debugger on junk bytes that the engine has saying is bad input!!! Real problem is the following: Test case generate bytes and convert them to UTF-8 using ICU (please correct if I'm wrong, Dmitry K.). But the generated UTF-8 bytes is not valid UNICODE_FSS. Current, well formed check of UNICODE_FSS is done as with UTF-8, so string pass from a stage that it shouldn't. Later, when converting from (wrong) UNICODE_FSS to TIS620 a transliteration error is raised.
So what really need to be fixed is UNICODE_FSS well formed check, and then ask for Dmitry correct its tests. :-) This is at least for blob.002.unicode.TBL_CS__TIS620.COL_BLOB.ins_UNICODE_FSS.sel_TIS620.len_32767.chars_TIS620.bind__wstr case. Didn't verified others yet. See attach file
But I continue get the old (and new) errors with select from TBL_CS__CP943C as UNICODE_FSS I think this problem has link with >and then ask for Dmitry correct its tests. :-)
No problem, Adriano. I has improved my tests. But has get the new, similar errors for all FB-charsets :-( Ofcourse, except ASCII [ FB 2.1.1 without filters__dirty_patch ] |
|||||||||||||||||||||||||||||||||||||||||||||||||||