Subject | Trouble with updating security database (1.5 to 2.0) |
---|---|
Author | ainpoissee |
Post date | 2006-11-23T10:45:16Z |
Hi,
The security database upgrade script (security_database.sql) fails
when user name (USER_NAME field) contains non ASCII character(s). In
my case it was "รค" (a umlaut), haven't tested with other characters.
The script reports
Statement failed, SQLCODE = -802
arithmetic exception, numeric overflow, or string truncation
-Cannot transliterate character between character sets
After line 109 in file E:\...\security_database.sql
error and content of the security database is lost.
If the script can't be enchanched to coupe with this situation at
least warning in rlnotes / security_database.txt would be good.
Also, if user name may contain only ASCII characters servises API
should check for this (I'm prety sure the user name in question was
added via API).
TIA
ain
The security database upgrade script (security_database.sql) fails
when user name (USER_NAME field) contains non ASCII character(s). In
my case it was "รค" (a umlaut), haven't tested with other characters.
The script reports
Statement failed, SQLCODE = -802
arithmetic exception, numeric overflow, or string truncation
-Cannot transliterate character between character sets
After line 109 in file E:\...\security_database.sql
error and content of the security database is lost.
If the script can't be enchanched to coupe with this situation at
least warning in rlnotes / security_database.txt would be good.
Also, if user name may contain only ASCII characters servises API
should check for this (I'm prety sure the user name in question was
added via API).
TIA
ain