Subject Re: [Firebird-Architect] Multi Connection meta data update
Author Dmitry Yemanov
"kartinku" <kartinku@...> wrote:
> I commented out exclusive connection check for my application to
> enable FK creation at multi connection. I feel it is not proper.
> There would be any reason behind this constraint.

Of course. You shouldn't be able to modify table data while the constraint
(actually, an index which supports this constraint) is being created.

> Please do let me know what is the reason (design) for not supporting
> foreign key creation even in super server in multi connection scenario.

See above. IMO, the proper (more or less) solution would be to just
exclusively lock both tables being affected. This should work in both SS and
CS builds. An exclusive lock on the entire database is too much. But Ann may
be right in her doubts about the improper CS metadata cache updates, this
issue requires testing.