Subject | Re: line generating transliteration exception in FB stored proc code (unicode) |
---|---|
Author | Roman Rokytskyy |
Post date | 2004-01-04T19:28:16Z |
Hi,
so engine cannot return you such information.
character set did not cause automatic character set assignment for
character columns/params. However I do not remember to which engine is
this related (probably it was introduced in some RC and fixed in one
of the next RCs).
Best regards,
Roman Rokytskyy
> I want to know where was an illegal transliteration, I mean line ofAs far as I know BLR code does not contain line numbers for debugging,
> code in Firebird (procedures are rather complicate, call one
> another). Is it possible to find it out?
so engine cannot return you such information.
> the database was made with default encoding UNICODE_FSS.I remember, there was a bug, that creating a database with default
character set did not cause automatic character set assignment for
character columns/params. However I do not remember to which engine is
this related (probably it was introduced in some RC and fixed in one
of the next RCs).
Best regards,
Roman Rokytskyy