Backward compatibility issues with schemas

[aafemt]

Mark is right, it was offtopic in #8605 but I'm sure that the problem is more general than just character set and collations. RDB$DATABASES is already under discussion and I'm sure that other system tables will follow.

Try creating two tables with the same name in different schemas in IBExpert. It will be very funny.

And it is a good example proving that this schema PR has a wrong design, done in a wrong way and committed prematurely.

No. This is just an argument not to use features that are not supported by your application. You can prohibit this in different ways, for example in a DDL trigger, if necessary.

Is there any reason why RDB$RELATIONS had to be modified to include schemas at all? Have you ever decided it to become a view for backward compatibility only, over a brand new set of system tables? In this case old system tables can reflect only objects in single (current or PUBLIC) schema and every old tool will work just fine.

[mrotteveel]

I think this is more something to discuss on firebird-devel.

[aafemt]

The audience here is wider. More opinions, more ideas.

[AlexPeshkoff]

What I agree with is that we need more generic solution than only for charsets/collations. Modifying Mark's example:

create schema breaking_things;
set search_path to public,breaking_things,system;
create table breaking_things.rdb$relations (rdb$relation_name char(64) character set utf8, rdb$relation_id smallint);
select * from rdb$relations;

returns empty result set. On my mind we should make generic solution - do we try to avoid such behavior or not.

[asfernandes]

It would have more sense to revert schemas PR and delete the code than going this way.

[mrotteveel]

A general solution IMHO doesn't make sense at all. The reason I'm arguing for an exception for character sets and collations is because of how they are used in normal queries, and how you need them to be always available, contrary to all other system objects..

[asfernandes]

Should I file a bug that if user does sudo rm -rf /opt/firebird Firebird no longs work correctly?