Subject | Re: Non - printable characters in Stored Procedures |
---|---|
Author | peter_jacobi.rm |
Post date | 2003-11-05T10:35:12Z |
Hi Tim, All,
--- Tim Ledgerwood <tim@s...> wrote:
undersupported, to put it mildly. And for some reason,
as it is a possible unsave operation.
To put in the language of True Believers:
Once you are tainted with mark of CHARSET NONE,
there is no way back but to start from scratch.
In practice there is a traditional hack using the system
tables, but I'll check this mayself before advertizing it.
The best option may be, to rely on the hard work of
our valued tool authors (Martijn?!), who most likely
have a shrink-wrapped solution.
Regards,
Peter Jacobi
--- Tim Ledgerwood <tim@s...> wrote:
> So now how do I convert a db with a default 'NONE' charset tosomething I
> can use? How do I choose what I should be using?You've got me here. In current FB this is somewhat
undersupported, to put it mildly. And for some reason,
as it is a possible unsave operation.
To put in the language of True Believers:
Once you are tainted with mark of CHARSET NONE,
there is no way back but to start from scratch.
In practice there is a traditional hack using the system
tables, but I'll check this mayself before advertizing it.
The best option may be, to rely on the hard work of
our valued tool authors (Martijn?!), who most likely
have a shrink-wrapped solution.
Regards,
Peter Jacobi