What MySQL-flavor to choose.

We are about to migrate from MySQL 4.1 to a 5.5 version. We heavily use InnoDB, have an dual quad Nahelem Xeon, 24GB DDR3, 4*SSD in RAID-10 on an Adaptec RAID with 512MB Cache and running under x64 Linux on a modern kernel. We replicate to several other slaves. I only have experience on vanill

Re: What MySQL-flavor to choose.

On 2011-02-14 15:31, Singer X.J. Wang wrote: What is your load type? Heavy read but enough write not to benefit much from query cache. It is a webshop app (custom). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?u

RE: How to export data with column names?

>-Original Message- >From: mos [mailto:mo...@fastmail.fm] >Sent: Sunday, February 13, 2011 4:50 PM >To: mysql@lists.mysql.com >Subject: How to export data with column names? > >I want to use > >select * into outfile "myfile.txt" from table1; > >and have it export the data as tab delimited b

Re: What MySQL-flavor to choose.

On 2011-02-14 15:43, Singer X.J. Wang wrote: So I'm assuming OLTP type transaction, then I'm going to recommend MySQL 5.5. Why is that flavor to be chosen over MariaDB with XtraDB or Percona with XtraDB? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubsc

Re: What MySQL-flavor to choose.

According to the benchmarks on the Personal website, the 5.1 version of Persona has the same about performance as mysql 5.5 (http://www.percona.com/software/benchmarks/) Also the 5.5 version of the Persona(not reported as stable) is even better than mysql 5.5 according the the same site. Also aft

CR: add support of interactive transactions for webclients

CR: add support of interactive transactions for webclients Hello, I dont know how to place an idea (CR) for mySQL. I try it that way. At the moment I am implementing an "easy-to-use" multiuser webclient for database usage. (phpMyAdmin in contrast is a very powerful tool for people with technical

Re: What MySQL-flavor to choose.

Hi, > Also after reading Dimitrik blog > (http://dimitrik.free.fr/blog/archives/2010/07/mysql-performance-innodb-io-capacity-flushing.html), > its seems to me , than one of the thing that are different between the > stock mysql (5.5) and xtradb, is the way that they handle IO capacity > and flush.

Re: What MySQL-flavor to choose.

According to http://dimitrik.free.fr/blog/archives/2010/12/mysql-performance-analyzing-perconas-tpcclike-workload-on-mysql-55.html the xtraDB is ignoring the io capacity setting. But this of course it might be just a minor bug in the percona version that dimitriK used in his test..:-) akops On 1

Insert only if the entry doesn't exist

Hi all, Thanks for your fast answer to my last question! Here's one more problem I commonly deal with. There are cases when I need to insert the row only if such a row doesn't exist, otherwise I need either to update the row or to do nothing, just skip the query. The common case is the rat

Re: Insert only if the entry doesn't exist

Instead of "insert into" you can use "replace into". -- João Cândido de Souza Neto "Andre Polykanine" escreveu na mensagem news:1621362474.20110214201...@oire.org... Hi all, Thanks for your fast answer to my last question! Here's one more problem I commonly deal with. There are cases when

RE: Insert only if the entry doesn't exist

Be Careful. REPLACE INTO mechanically does DELETE and INSERT under mysqld's hood. If you want to do nothing if row exists already then do: INSERT IGNORE instead of REPLACE INTO Rolando A. Edwards MySQL DBA (SCMDBA) 155 Avenue of the Americas, Fifth Floor New York, NY 10013 212-625-5307 (Work) 2

Re: Insert only if the entry doesn't exist

Hello Rolando, Sorry, but if I do INSERT IGNORE INTO, then I must indicate a key (typically a unique key or a primary key), or is it false? But I don't know that key and no way to get it without more queries... -- With best regards from Ukraine, Andre Skype: Francophile My blog: http://oire

RE: Insert only if the entry doesn't exist

If the table has Primary and/or UNIQUE Keys, then you are fine. You do not need to know what they are. If you want to see them do this: SHOW CREATE TABLE Votes\G INSERT IGNORE INTO does not require ON DUPLICATE KEY options. After all, you said earlier that you want to do nothing if the row exists

Foreign Key Error

Hi; I have this command: create table if not exists categoriesRelationships (ID integer auto_increment primary key, Store varchar(60), Parent integer not null, foreign key (Parent) references categories (ID), Child integer not null, foreign key (Child) references categories (ID)) engine=innodb; s

Re: Insert only if the entry doesn't exist

Hello Rolando, So if I do "INSERT IGNORE INTO `Votes` SET `EntryId`='12345', UserId`='789'"; it *won't* insert the second row if there's a row with EntryId set to 12345 and UserId set to 789? Thanks and sorry!) -- With best regards from Ukraine, Andre Skype: Francophile My blog: http://oire.org

RE: Foreign Key Error

" or column types in the table and the referenced table do not match for constraint" The columns Parent and Child are signed integers and ID is unsigned. Regards, Gavin Towey -Original Message- From: Victor Subervi [mailto:victorsube...@gmail.com] Sent: Monday, February 14, 2011 3:09 P

Re: Foreign Key Error

Thank you! V On Mon, Feb 14, 2011 at 9:08 PM, Gavin Towey wrote: > " or column types in the table and the referenced table do not match for > constraint" > > The columns Parent and Child are signed integers and ID is unsigned. > > Regards, > Gavin Towey > > -Original Message- > From: Vi