[Open-bio-l] FK cascades

[Chris Mungall]

On Wed, 21 Aug 2002, Hilmar Lapp wrote:

> Maintaining is FK integrity in the SW layer is not only inevitably
> unsafe and prone to slip, it also makes for _ugly_ code in the
> adaptors.

agreed

> I don't know exactly what Postgres is capable of, but I'd assume it
> enforces FK constraints and can do cascading deletes. Oracle does.
> It seems InnoDB from one of the most recent versions on can do, too.

postgres does indeed either enforce or do cascading deletes

> How much outcry would it cause to require MySQL-Max > 3.23.50 to run
> BioSQL, and then migrate to using InnoDB as the table handler?
> (There are couple problems with the InnoDB implementation of FK
> constraint enforcement, but if no-one messes with the table
> definitions and the order they are created, these can be handled I
> believe.)

I don't know enough about InnoDB to comment. we're still using myisam at
berkeley coz we haven't had time to look into changing. how does it
compare speed-wise to MyISAM?

it would be nice to get rid of all that pointless adapter code

> 	-hilmar
>
> (Still cross-posting, but soon I'll post to the biosql-list only.
> Hopefully I'm not going to be alone there ...)
>
> --
> -------------------------------------------------------------
> Hilmar Lapp                            email: lapp at gnf.org
> GNF, San Diego, Ca. 92121              phone: +1-858-812-1757
> -------------------------------------------------------------
>
> _______________________________________________
> Open-Bio-l mailing list
> Open-Bio-l@open-bio.org
> http://open-bio.org/mailman/listinfo/open-bio-l
>