Subject Re: [firebird-support] Re: DDL Statements question.
Author Martijn Tonies

> I hope problem is due to "multi connection meta data update" constraint.

There are multiple reasons for this:

1) multiple connections. In Database Workbench, the SQL/Script
Editor uses a secondary connection by default, which results in
errors like these. You can turn this off in the Preferences.
This behaviour is needed for multi-threading the SQL Editor.

2) Trying to create FKs for uncommitted tables. In Database
Workbench, use the "autocommit" flag in the Script Editor to
overcome this problem.

> In firebird when there are multiple connection (more than one) to
> same Database. Create foreign key will throw this error. Foreign key
> can be created when there is single connection.
> Firebird have this due to its design constraint. When there are more
> than one connection notification between differrent process(In classic
> server for each connection a sperate process will be spawn) is an
> problem in classic server mode. so what they have this constraint. But
> I don't get why they have this constarint even for super server.
> I modified the code (commeneted out the exclusive connection check
> in firebird source and rebuilt the firebird for my application).

I would recommend against this! So does everyone else ;-)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Upscene Productions