Multibyte CHAR value requested as VARCHAR is returned with padded spaces. [CORE2606] #3016
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
|
Commented by: @asfernandes This is not "blocker". This problem is present since 2.0, and FWIW many people does not even notice it. It was discussed a number of times, and my hope is to have a fix in v3.0. |
Modified by: @asfernandespriority: Blocker [ 1 ] => Major [ 3 ] |
|
Commented by: @asfernandes Also, 1.5 is wrong in many cases with MBCS. You can't say it's right in a so small test case. Just tries an union of 'A' with '<some multibyte char>' and see. |
|
Commented by: Tsutomu Hayashi (tomneko) Hi Adriano It is not blocking the engine, but blocking migration from old applications or other databases. I tested my web application from fb1.5 to fb2.1, but this blocked migration. I tested MySQL and PostgreSQL, these are no problem. SUMMARY: CHAR Type <Client UTF8> <Client ASCII> VARCHAR Type <Client UTF8> <Client ASCII> * SJIS_0208 and EUCJ_0208 returns 'A ', so these are 2 byte set. |
Modified by: @dyemanovFix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @asfernandessummary: Select Literal returns right pad string => Multibyte CHAR value requested as VARCHAR is returned with padded spaces. |
Modified by: @asfernandesVersion: 3.0 Initial [ 10301 ] |
|
Commented by: @asfernandes Now when user request the value as VARCHAR (SQL_VARYING), the correct length is returned. |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Tsutomu Hayashi (tomneko)
Is related to QA545
Votes: 1
ON UTF8 CLIENT:
SELECT 'A' FROM RDB$DATABASE;
returns 'A '
ON SJIS_0208 CLIENT:
returns 'A '
* FB1.5 returns 'A' in any cases.
Commits: c081b76
The text was updated successfully, but these errors were encountered: