That should have been `in (14, 37)`. I think I should stop thinking for
the rest of the day...
Interestingly, 2 occurs with character set id 2 (ASCII), and 3 occurs
with character set id 4 (UTF8), and given previously types using UTF8,
used UNICODE_FSS (character set id 3), I wonder if there is some
relation there, especially as RDB$TYPES contains an entry SQL_TEXT with
id 3).
However, that then makes me wonder if SQL_TEXT shouldn't be changed to
ID 4 (as the SQL standard says: "SQL_TEXT is a character repertoire that
is an implementation-defined (IA016) subset of the repertoire of the
Universal Character Set that includes every <SQL language character> and
every character in every character set supported by the
SQL-implementation. The name of the default collation is SQL_TEXT;"
(And UNICODE_FSS is not that subset of "every character in every
character set supported by the SQL-implementation", as it misses a
significant part of UTF8).
Mark
--
Mark Rotteveel