You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regression in FB 4.x: error "Implementation of text subtype <NNNN> not located" on attempt to use some collations defined in fbintl.conf [CORE6336]
#6577
Content of this file is the same in FB 3.x and 4.x.
I've created SQL script which tries to:
* create DB with each of these charsets,
* alter charset with assigning new default collation to it (for every collation that are defined for this charset), i.e.:
alter character set DOS437 set default collation DB_US437;
* create view with trivial DDL:
recreate view v_info as select f.rdb$field_name as f_name from rdb$fields f where f.rdb$field_name = upper('dm_name');
Main problem: there are lot of collations which can not be used anymore in 4.x: RECREATE VIEW issues "Implementation of text subtype <NNNN> not located".
Also, one may to see that almost all charsets actually have *no* collation with suffix = "_UNICODE", e.g:
-ALTER CHARACTER SET DOS437 failed
-COLLATION DOS437_UNICODE for CHARACTER SET DOS437 is not defined
( except tis620, gbk, cp943c and gb18030 - they *do* have such collations)
SQL and logs see in attached .7z
Checked on Windows 8.1 x64, FB: 3.0.6.33312; 4.0.0.2066
Submitted by: @pavel-zotov
Attachments:
check-collations-from-fbintl-conf_-_SQL-and-logs-for-3x-4x.7z
File %FB_HOME%\intl\fbintl.conf has content with definitions of miscelaneous charsets and their collations, e.g.:
charset = DOS437 {
intl_module = fbintl
collation = DOS437
collation = DOS437_UNICODE
collation = DB_DEU437
. . .
}
charset = DOS850 {
intl_module = fbintl
collation = DOS850
collation = DOS850_UNICODE
. . .
}
. . .
Content of this file is the same in FB 3.x and 4.x.
I've created SQL script which tries to:
* create DB with each of these charsets,
* alter charset with assigning new default collation to it (for every collation that are defined for this charset), i.e.:
alter character set DOS437 set default collation DB_US437;
* create view with trivial DDL:
recreate view v_info as select f.rdb$field_name as f_name from rdb$fields f where f.rdb$field_name = upper('dm_name');
Main problem: there are lot of collations which can not be used anymore in 4.x: RECREATE VIEW issues "Implementation of text subtype <NNNN> not located".
Also, one may to see that almost all charsets actually have *no* collation with suffix = "_UNICODE", e.g:
-ALTER CHARACTER SET DOS437 failed
-COLLATION DOS437_UNICODE for CHARACTER SET DOS437 is not defined
( except tis620, gbk, cp943c and gb18030 - they *do* have such collations)
SQL and logs see in attached .7z
Checked on Windows 8.1 x64, FB: 3.0.6.33312; 4.0.0.2066
Commits: 32d61ff
The text was updated successfully, but these errors were encountered: