SUBSTRING of non-text/-blob is described to return NONE character set in DSQL [CORE6160] #6409
Comments
|
Commented by: Sean Leyne (seanleyne) Adriano, it seems odd that ASCII character set would be used. I would have expected the character set to be, either: (a) the character set of the database [but I don't see that value exposed anywhere], or (b) the character set of the DB connection, |
|
Commented by: @asfernandes If DB and connection charset are none, it would be described as NONE. Always using ASCII (as numbers/dates are representable on it) it's more complete IMO. But if connection charset is something else, DSQL will convert and describe with the connection charset, as it does with everything. |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @asfernandes
The correct character set should be ASCII.
set sqlda_display on;
select substring(1 from 1 for 1) from rdb$database;
select substring(current_date from 1 for 1) from rdb$database;
Commits: 327c642 329a5c0
The text was updated successfully, but these errors were encountered: