Re: replication from InnoDB to MyISAM

[EMAIL PROTECTED] schrieb: anyone know if there's any known issue with replication from InnoDB tables to MyISAM tables? I just switched a slave (mysql) to replicate from a different master that uses InnoDB and now I'm seeing weird problems on the slave. Table corruption, apps that can't conn

replication from InnoDB to MyISAM

anyone know if there's any known issue with replication from InnoDB tables to MyISAM tables? I just switched a slave (mysql) to replicate from a different master that uses InnoDB and now I'm seeing weird problems on the slave. Table corruption, apps that can't connect etc. thanks, Jeff --

How to convert InnoDB to MyISAM in 5.0?

hi guys, it's a simple thing (I think), but I can't find the docu on this from the mysql site. Thanks in advance for the help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: How long does it take to change engine from innodb to myisam?

o by in order to estimate how long it would > take to change over from innodb to myisam. Say for a 100meg file, a 5 > gig table, etc. > > Thank you; > -nat > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored b

How long does it take to change engine from innodb to myisam?

Hi; Is there a formula I can go by in order to estimate how long it would take to change over from innodb to myisam. Say for a 100meg file, a 5 gig table, etc. Thank you; -nat -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com

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: Alter InnoDB to MyISAM Part2

"Scott Purcell" <[EMAIL PROTECTED]> wrote on 05/25/2005 09:22:32 AM: > I can do this programatically, and will alter the table. But there > are three tables that have foreign key references to the table I > will be altering. > > They look like this. > CREATE TABLE ITEM_CAT_REL ( > id INT,

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 newtab

Re: Alter InnoDB to MyISAM Part2

quot;Scott Purcell" <[EMAIL PROTECTED]> To: Sent: Wednesday, May 25, 2005 6:22 AM Subject: Alter InnoDB to MyISAM Part2 I can do this programatically, and will alter the table. But there are three tables that have foreign key references to the table I will be altering. They look li

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&#

Alter InnoDB to MyISAM Part2

I can do this programatically, and will alter the table. But there are three tables that have foreign key references to the table I will be altering. They look like this. CREATE TABLE ITEM_CAT_REL ( id INT, cat_id INT NOT NULL, key(id), FOREIGN KEY (id) references ITEM(id) on

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

InnoDB to MyISAM

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. How can I convert the Inn

Re: Changed Logging Table from InnoDB to MyIsam, what memory buffers to tune?

e finally split our huge logging aspect of an application to its own = > system, and we changed the table type from InnoDB to MyIsam. This is a = > logging table, 1 log writer, many, many selects from customer care reps = > looking up the last 500 or so records. These are logs of timed

Changed Logging Table from InnoDB to MyIsam, what memory buffers to tune?

We finally split our huge logging aspect of an application to its own system, and we changed the table type from InnoDB to MyIsam. This is a logging table, 1 log writer, many, many selects from customer care reps looking up the last 500 or so records. These are logs of timed events, so they