Subject RE: [Firebird-Java] How to turn referential integrity checking off
Author Rick Debay
ALTER TABLE <table name> ALTER CONSTRAINT <foreign key name> INAVTIVE
Dynamic SQL Error SQL error code = -104 Token unknown - line 1, char 37
CONSTRAINT

Although it might be implemented by turning off the trigger that
enforces it.

Rick DeBay

-----Original Message-----
From: Firebird-Java@yahoogroups.com
[mailto:Firebird-Java@yahoogroups.com] On Behalf Of Roman Rokytskyy
Sent: Friday, September 30, 2005 2:28 AM
To: Firebird-Java@yahoogroups.com
Subject: Re: [Firebird-Java] How to turn referential integrity checking
off

> All these cases can be addressed by the simple expedient of declaring
> a foreign key inactive.

If application developer has names of all foreign keys, it no longer
matters what to execute:

ALTER TABLE <table name> ALTER CONSTRAINT <foreign key name> INAVTIVE;

or

ALTER TABLE <table name> DROP CONSTRAINT <foreign key name>

The talk is about a global switch that triggers all constrains inactive
without a need to walk through all system tables and deactivating each
constraint separately.

Roman



------------------------ Yahoo! Groups Sponsor --------------------~-->
Most low income households are not online. Help bridge the digital
divide today!
http://us.click.yahoo.com/cd_AJB/QnQLAA/TtwFAA/saFolB/TM
--------------------------------------------------------------------~->


Yahoo! Groups Links