Subject | Re: [firebird-support] From Restriced to CASCADE on delete |
---|---|
Author | Nando Dessena |
Post date | 2008-01-16T11:30:40Z |
Helen,
H> Did you create this constraint in Oracle? It's interesting that
H> the DDL engine tolerates it - might be some blast from the past.
H> :-) At the moment you have NO ACTION (the default) defined. Other
H> options available are CASCADE, SET DEFAULT and SET NULL.
FWIW Firebird allows both RESTRICT and NO ACTION, and differentiates
between them in the system tables (i.e. it is able to rebuild an ADD
CONSTRAINT statement correctly). AFAIR IB always has.
The two have (subtly) different behaviour in SQL-compliant databases,
but I suspect that Firebird treats them both as NO ACTION. No time to
perform a test right now.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
H> Did you create this constraint in Oracle? It's interesting that
H> the DDL engine tolerates it - might be some blast from the past.
H> :-) At the moment you have NO ACTION (the default) defined. Other
H> options available are CASCADE, SET DEFAULT and SET NULL.
FWIW Firebird allows both RESTRICT and NO ACTION, and differentiates
between them in the system tables (i.e. it is able to rebuild an ADD
CONSTRAINT statement correctly). AFAIR IB always has.
The two have (subtly) different behaviour in SQL-compliant databases,
but I suspect that Firebird treats them both as NO ACTION. No time to
perform a test right now.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================