Purpose of RDB$FUNCTION_NAME in RDB$CHARACTER_SETS and RDB$COLLATIONS, and does it need schema support

10 views
Skip to first unread message

Mark Rotteveel

unread,
Mar 16, 2026, 9:35:39 AM (yesterday) Mar 16
to firebir...@googlegroups.com
The RDB$CHARACTER_SETS and RDB$COLLATIONS tables have a column
RDB$FUNCTION_NAME.

The language reference documents it for RDB$CHARACTER_SETS as:

"""
For a user-defined character set that is accessed via an external
function, the name of the external function
"""

And for RDB$COLLATIONS as:

"""
Not currently used
"""

Is this in anyway still supported (if ever)?

If so, shouldn't they also receive a RDB$FUNCTION_SCHEMA_NAME to point
to the declaration of the external function in RDB$FUNCTIONS?

If not, shouldn't this column simply be removed from both tables?

Mark
--
Mark Rotteveel

Dmitry Yemanov

unread,
Mar 16, 2026, 10:14:35 AM (yesterday) Mar 16
to firebir...@googlegroups.com
16.03.2026 16:35, 'Mark Rotteveel' via firebird-devel wrote:
>
> If not, shouldn't this column simply be removed from both tables?

Even if unused, they may be queried by connectivity drivers and they may
be outdated/unsupported to fix/adjust them easily. I always treat the
existing system schema as a lifetime contract with users and breaking it
just for cleanup is not something I'd support.


Dmitry

Mark Rotteveel

unread,
Mar 16, 2026, 10:30:48 AM (yesterday) Mar 16
to firebir...@googlegroups.com
Well, if it is truly unused, we could also consider at least changing
the type to a domain, e.g. "RDB$UNUSED_NAME", declared as CHAR(1)
CHARACTER SET ASCII and save 251 bytes in the in-memory image of each row ;)

Mark
--
Mark Rotteveel
Reply all
Reply to author
Forward
0 new messages