Subject | Re: [firebird-support] Re: Is this a bug or intended behaviour? |
---|---|
Author | Ann W. Harrison |
Post date | 2010-06-25T21:20:13Z |
Thomas wrote:
and they got a number things right. If you can do deferred constraints,
statement level constraints are easy (sort of). For what little it
matters, MySQL has foreign keys only in InnoDB and they won't handle
this case either.
Firebird and PostgreSQL - if I've guessed right about your other
database. I think Oracle has cascading delete ... but not cascading
update.
order, regardless.
Good luck,
Ann
>Yes, Postgres implemented foreign keys several years after InterBase
>
> I was only a bit surprised as the other databases, that I'm using got this "right".
> So my expectactions were set..
and they got a number things right. If you can do deferred constraints,
statement level constraints are easy (sort of). For what little it
matters, MySQL has foreign keys only in InnoDB and they won't handle
this case either.
>Another alternative is to use cascading deletes, which work in both
Firebird and PostgreSQL - if I've guessed right about your other
database. I think Oracle has cascading delete ... but not cascading
update.
>> Did you tryRight. Stupid of me. It's going to try the delete in storage
>> delete from fktest where id in (4, 3, 2, 1);
>
> No difference.
order, regardless.
Good luck,
Ann