I have been reading the definitive guide to MySQL5, and I am not finding
a answer to a question.
I am designing a project in which I am going to have primary keys, and
foreign keys. In order to keep things proper, I am going to have delete
on cascades on my foreign keys, so when the primary
Hi Scott,
Indeed, only the BDB and InnoDB storage engines support referential
integrity. If you accidentally create the table as MyISAM, there is
no error, though -- the constraints serve as a comment.
Replication is storage-engine independent, so you shouldn't have a
problem with that.
As I have been reading, it appears that the InnoDB Storage Engine
supports PK/FK relationships. And that the MyISAM does not. But I cannot
verify that.
That is correct.
Martijn Tonies
Database Workbench - development tool for MySQL and more!
Upscene Productions
http://www.upscene.com
My
Hello Sheeri,
Indeed, only the BDB and InnoDB storage engines support referential
integrity. If you accidentally create the table as MyISAM, there is
no error, though -- the constraints serve as a comment.
No error? A comment? What use is that?
If you want FKs, having the FKs as a comment
I didn't write the codebase for MySQL, so it's pointless to tell me
that it's useless to be able to create a foreign key on a MyISAM
table. I agree that it's useless, however, it's possible, which is
why I put it in there -- as a caveat.
The use is that apparently in future versions MyISAM will
are the same;
in practice they are not.
On Fri, 31 Mar 2006, sheeri kritzer wrote:
To: Martijn Tonies [EMAIL PROTECTED]
From: sheeri kritzer [EMAIL PROTECTED]
Subject: Re: Table Type For PK/FK
I didn't write the codebase for MySQL, so it's pointless to tell me
that it's useless to be able
