Subject Re: line generating transliteration exception in FB stored proc code (unicode)
Author Roman Rokytskyy
Hi,

> I want to know where was an illegal transliteration, I mean line of
> code in Firebird (procedures are rather complicate, call one
> another). Is it possible to find it out?

As far as I know BLR code does not contain line numbers for debugging,
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