Actually, you *do* need them if the need is to conform to a standard of
some sort that requires foreign keys. I've worked for a few places where
this was the case. Granted the spec could be changed, but most times you
won't have that option.
###############################
Ian J. Alexander <[EMAIL PROTECTED]>
Senior Software Engineer
EazeNet
817-557-3038
###############################
On Mon, 17 Jan 2000, Jason Costomiris wrote:
> On Mon, Jan 17, 2000 at 10:32:32AM -0600, Alan Mead wrote:
> : If COMMIT and ROLLBACK are important or
> : you need "true" foreign keys, then you probably need postgresql (I think
> : there are workarounds on the mysql website).
>
>
> You're correct with respect to support for transactions..
>
> However, don't kid yourself.. Nobody *needs* foreign keys.. If your
> code manages its data properly, you'll never need 'em. :)
>
> --
> Jason Costomiris <><
> Technologist, cryptogeek, human.
> jcostom {at} jasons {dot} org | http://www.jasons.org/
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
