On 11-5-2019 00:06, Lester Caine lester@... [firebird-support] wrote:

> For 20 odd years I've only ever created databases with a charset of NONE
> and because of the way PHP works the odd UTF8 string just works as raw
> data. Strange names and address strings just work and there is normally
> only a problem when the string was corrupt anyway.
>
> Now I think it's time I started to look at tidying things up, and move
> to UTF8 as the default character set. I've various notes across several
> versions of FB, but is there a good current crib sheet on how to handle
> this? I think I'm simply looking at creating a new empty UTF8 copy of
> the database and pumping over from the NONE version?

Not that I'm aware of. Creating a new database and pumping the data is
the best approach. Make sure to verify your migration process before
getting rid of the old database.

Mark
--
Mark Rotteveel