Attachment: bug.png [ 11939 ]

Attachment: correct.png [ 11940 ]

description: This issue is more noticeable in Linux, which generally uses terminal configured to UTF-8.

But it exists for all OSes, and it's not specific to console, but to any file the data is output.

ISQL pads UTF-8 data and separators as each UTF-8 byte being a character.

Attached is two images, with bug and correct behavior.

This issue exists for any multibyte character set, but I'm fixing it in ISQL for UNICODE_FSS and UTF8.

=>

This issue is more noticeable in Linux, which generally uses terminal configured to UTF-8.

But it exists for all OSes, and it's not specific to console, but to any file the data is output.

ISQL pads UTF-8 data and separators as each UTF-8 byte being a character.

Attached is two images, with bug and correct behavior.

This issue exists for any multibyte character set, but I'm fixing it in ISQL for UNICODE_FSS and UTF8.

Test case
--------------------
create or alter procedure p1 returns (
c1 char(5) character set utf8,
c2 char(10) character set utf8,
vc1 varchar(5) character set utf8,
vc2 varchar(10) character set utf8
)
as
begin
vc1 = '12345';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;

vc1 = 'áé';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;

vc1 = '123';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;

vc1 = '12345';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;

vc1 = '1234';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;

vc1 = 'áéíóú';
c1 = vc1;
c2 = vc1;
vc2 = vc1;
suspend;
end!
select * from p1!
--------------------

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

Link: This issue is related to QA565 [ QA565 ]

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: Done successfully

Test Details: Padding in WI-T3.0.0.31767 looks OK: checked output on NotePad++ 6.6.9

status: Resolved [ 5 ] => Closed [ 6 ]