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 star
On 11-5-2019 00:06, Lester Caine les...@lsces.uk [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
>
Guten Tag Lester Caine les...@lsces.uk [firebird-support],
Strings with charset none need only 1 byte per char in the receive buffer of
your software
UFT-8 will reserve 4 Bytes per char , regardless if it is needed or not ,
this can cause some problems on larger records
> For 20 odd years I've
On 11/05/2019 07:27, Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] wrote:
>> 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 approac
On 11/05/2019 07:54, Hannes Streicher hstreic...@gmx.de
[firebird-support] wrote:
> Guten Tag Lester caineles...@lsces.uk [firebird-support],
>
> Strings with charset none need only 1 byte per char in the receive buffer of
> your software
> UFT-8 will reserve 4 Bytes per char , regardless if it
