On 29.06.2017 at 19:15, Tomasz Tyrakowski t.tyrakowski@...
[firebird-support] wrote:

> On 28.06.2017 at 22:58, Ann Harrison aharrison@...
> [firebird-support] wrote:
> [...] > Or is 3 strictly bound
> to PXW_PLK and always means PXW_PLK, regardless of the character set of
> the database? I suppose this is not the case, 'cause setting a column
> collation to WIN1250 in a database with the default character set
> WIN1250 results in RDB$COLLATION_ID = 0 (and I don't think WIN1250 is so
> special as to be given the value of 0).
> On a second thought, don't waste your time on it. I'll just create those
> two DBs, see for myself, and post a quick update.

OK, I probably had it coming ;)
Obviously you can't create a database with the character set WIN1252 and
then set the collation of a column to WIN1250 or PXW_PLK. No wonder the
only result you get is an error message.
So my last question was plain stupid, but updating RDB$COLLATION_ID and
then a backup-restore is still a temptation...

thanks and best regards
Tomasz