|Subject||Re: [Firebird-Java] Re: How to turn referential integrity checking off|
> The problems result during the creation of the tables themselves. If aThat is right... Now all pieces are together in my head :)
> CREATE TABLE statement has a "REFERENCES 'primaryKeyTableName'
> ('primaryKeyTableColumn')" clause and that 'primaryKeyTable' has not
> been created yet, such a CREATE TABLE statement will cause an error
> because both the referenced table and its respective column cannot be
> found in the target database at that time.
> I have already constructed parts of the SQL statements with the helpIf you code is generic enough, would you please consider to publish it on
> of those methods.
our Wiki, so others can use it too?
> I have got the idea to construct such ALTER statements, ignoreIf you can strip the REFERENCES clauses from the original script, then half
> initially the REFERENCES parts when creating the tables,
of the job is already done :)
> then execute these ALTER statements when all tables have already beenAlso, I think that is the only portable approach for other databases.
> created and their data written in the target database. This may well solve
> my problem in a optimal way.