List:General Discussion« Previous MessageNext Message »
From:sheeri kritzer Date:March 31 2006 2:46pm
Subject:Re: Table Type For PK/FK
View as plain text  
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.  Basically it takes the commands from the binary
(update,delete,insert,replace) logs and applies them to the slave.

-Sheeri

On 3/31/06, Scott Purcell <spurcell@stripped> wrote:
> 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 key is deleted, the
> data model is kept clean.
>
>
>
> 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.
>
>
>
> Also, when I use replication, it appears that both engines, require a
> different replication technique? But what if I mix both types of
> engines, how do I replicate that?
>
>
>
> Sorry this is a bit of a broad post, but these two questions will help
> me figure my needs for the design.
>
>
>
> Thanks,
>
> Scott
>
>
>
Thread
Table Type For PK/FKScott Purcell31 Mar
  • Re: Table Type For PK/FKsheeri kritzer31 Mar
  • Re: Table Type For PK/FKMartijn Tonies31 Mar
  • Re: Table Type For PK/FKMartijn Tonies31 Mar
    • Re: Table Type For PK/FKsheeri kritzer31 Mar
      • Re: Table Type For PK/FKmysql31 Mar