Re: InnoDB to MyISAM

Nevertheless, foreign key constraints belong in the database, not in your application... If you have foreign keys (your wording), you need foreign key constraints. Period. Plain and simple. No discussion :-) How about a log database? We log every phone call to a calls table which currently has

Re: InnoDB to MyISAM

Peter Normann wrote: Martijn Tonies wrote: Nevertheless, foreign key constraints belong in the database, not in your application... If you have foreign keys (your wording), you need foreign key constraints. Period. Plain and simple. No discussion :-) Foreig

Re: InnoDB to MyISAM

> > Nevertheless, foreign key constraints belong in the database, not in > > your application... If you have foreign keys (your wording), you need > > foreign key constraints. Period. Plain and simple. No discussion :-) > > Foreign keys are foreign keys. Constraints are constraints. Foreign key >

RE: InnoDB to MyISAM

Martijn Tonies wrote: > Nevertheless, foreign key constraints belong in the database, not in > your application... If you have foreign keys (your wording), you need > foreign key constraints. Period. Plain and simple. No discussion :-) Foreign keys are foreign keys. Con

Re: InnoDB to MyISAM

> >> I think you're confusing referential constraints with foreign keys. > > > > In my book, referential constraints and foreign key constraints (the full > > name) > > are the same. > > Yes, referential constraints and foreign key constraints are the same thing. > Notice the word constraints. >

Re: InnoDB to MyISAM

I think you're confusing referential constraints with foreign keys. In my book, referential constraints and foreign key constraints (the full name) are the same. Yes, referential constraints and foreign key constraints are the same thing. Notice the word constraints. Let me say this again:

Re: InnoDB to MyISAM

Hi, If you're loocking for consurrent inserts/deletes, use innodb (row level locking). This will be better than myisam. I'm looking for concurrent inserts / selects, reading and writing. The key is to get the reads and blocking writes (writes that need the insert ID, which can't be done DELAY

Re: InnoDB to MyISAM

> >> >>key relationships? > >> > > >> > MyISAM can't FK's. > >> > >> Yes it can, they're just not enforced. > > > > LOL - that's just like saying that MyISAM supports transactions > > if you only do transactions that are a single statement... > > > > In other words: useles. > > Somehow I use these

Re: InnoDB to MyISAM

Hi, If you're loocking for consurrent inserts/deletes, use innodb (row level locking). This will be better than myisam. The text column can be created in aother table and stay referenced via a FK. This will ceratinly be faster since insert or delete on myisam implies a LOCK table implicit mecanis

Re: InnoDB to MyISAM

>>key relationships? > > MyISAM can't FK's. Yes it can, they're just not enforced. LOL - that's just like saying that MyISAM supports transactions if you only do transactions that are a single statement... In other words: useles. Somehow I use these "useles" foreign keys to create relational

Re: InnoDB to MyISAM

> > http://dev.mysql.com/doc/mysql/en/converting-tables-to-innodb.html > > He's converting InnoDB to MyISAM. > > I would recommend something like this: > > CREATE TABLE newtable LIKE oldtable; > > ALTER TABLE newtable ENGINE=MyISAM; > > ALTER TABLE newtable DISABLE KEYS; > > INSERT INTO newtable S

Re: InnoDB to MyISAM

- Original Message - From: "Rafal Kedziorski" <[EMAIL PROTECTED]> To: "Scott Purcell" <[EMAIL PROTECTED]>; Sent: Wednesday, May 25, 2005 6:06 AM Subject: Re: InnoDB to MyISAM http://dev.mysql.com/doc/mysql/en/converting-tables-to-innodb.html He&#

Re: InnoDB to MyISAM

hi, At 14:54 25.05.2005, Scott Purcell wrote: Hello, I posted last night but did not receive an answer. I am trying to create a fulltext index, but my table was created as an InnoDB type. There is quite a bit of data there (1000+ records) and I need to change to a MyISAM table for the indexi

Re: InnoDB to MyISAM

Scott Purcell wrote: Hello, I posted last night but did not receive an answer. I am trying to create a fulltext index, but my table was created as an InnoDB type. There is quite a bit of data there (1000+ records) and I need to change to a MyISAM table for the indexing for fulltext search. H