If I were to define a constraint on table B
CONSTRAINT DB_CONSTRAINT_REVERSE CHECK(
NOT EXISTS(
SELECT AID
FROM C
MINUS
SELECT AID
FROM B
)
it would guard against the delete but without deferred constraints it
would make inserting rows into either table B or C.
The same thing happens with foreign keys and is a feature of any
constraint creates relationships between tables.
So I quess that constraint checking at transaction boundary might be the
first step towards the full support of
database constraints.
This is just thought sharing .. no implications of anyone implementing
anything is made.
- rami
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
