Tomasz,
> One of the legacy databases I happen to maintain has character sets and
> collations messed up. [...]
For a database that is messed up like this, I'd go the clean way and
use a pump. That would also give you the opportunity to change it to
Unicode (UTF-8) at the same time, which is a
On 26.08.2016 o 14:35, robert rottermann rob...@redcor.ch
[firebird-support] wrote:
> I have no idea at on how to fix it "correctly", but would it not be an
> idea just to dump the tables with weird character into a text file, and
> search replace them.
>
> The wrong chars are probably uniformly
I have no idea at on how to fix it "correctly", but would it not be an
idea just to dump the tables with weird character into a text file, and
search replace them.
The wrong chars are probably uniformly wrong, so you should be able to
fix them using sed or some such tool (on linux, I am not
Hi,
One of the legacy databases I happen to maintain has character sets and
collations messed up. As far as I know, the database was created with
default character set "NONE" instead of "WIN1250", which should have
been set back then (and it's over 10 years old).
Then, some columns have been
