> AFAIK, issue is with Firebird's metadata tables - they are CHAR(31), not
> VARCHAR(31) and when you use them in your requests, they will be padded
> to 31-char length...

That shouldn't matter: if a VARCHAR is compared with a CHAR, the server
should treat both values as if they are CHAR and pad it the shortest value
to the length of the longest value before comparison.

I will check and propose a change if necessary. I also saw some other
processing in AbstractDatabaseMetadata that made me scratch my head but I
didn't have time to dive deeper.

--
Mark Rotteveel