May 26, 2012

Post: Benchmarking single-row insert performance on Amazon EC2

AUTO_INCREMENT=11073789 DEFAULT CHARSET=latin1 /*!50100 PARTITION BY RANGE (transactionid) (PARTITION p0 VALUES LESS THAN (100000000) ENGINE = InnoDB, PARTITION p1 VALUES

Post: AUTO_INCREMENT and MERGE TABLES

auto_increment value to be reused too. Can you use AUTO_INCREMENT clause in CREATE TABLE to get different auto_increment values ? I guess not: mysql> alter table am auto_increment

Post: Sharing an auto_increment value across multiple MySQL tables

auto_increment) engine=innodb; # each insert does one operations to get the value: INSERT INTO option1 VALUES (NULL); # $connection->insert_id(); Option #2: UseThe problem is that to be like most applications, we can’t really tell until a little concurrency is applied. Using only the

Post: Stored Function to generate Sequences

to “inject” the value to be returned next time this function is called. Sometimes people wonder why you would like to use sequences instead of MySQL auto_increment

Post: A workaround for the performance problems of TEMPTABLE views

… ) ENGINE=InnoDB AUTO_INCREMENT=2949071 DEFAULT CHARSET=latin1 1 row in set (0.00 sec) If we define a view which uses no …to this connection. When the table is inserted too (see below) the connection_id() function will be used to generate the value for the connection_id column. Also notice the

Post: How (not) to find unused indexes

be removed.  This method is flawed – here’s the first reason why: CREATE TABLE `sales` ( `id` int(11) NOT NULL AUTO_INCREMENTthe numbers “20-30%” as the minimum amount of rows you have to filter down to for an index to be useful

Post: Statement based replication with Stored Functions, Triggers and Events

AUTO INCREMENTAL VALUES In order to have the same auto incremental values on master and slaves the actual used auto incremental value is logged as an extra event just before the statement. MySQL uses the

Post: MySQL Users Conference - Innodb

… have in the index with current compression settings. The same utility could be used to advice on the compression page settings by looking at …auto-increment batch insert is not known as we do not have to allocate sequential auto increment values if row level replication is used. This however will be

Post: Efficient Boolean value storage for Innodb Tables

…1970324836974591 Index_length: 1024 Data_free: 0 Auto_increment: NULL Create_time: 2008-04-24…set (0.22 sec) Should you go and change all flags to use this approach ? I do not think so – for most applications using… many flag values to deal with which you can’t pack to the bitmask this approach can be

Post: Hacking to make ALTER TABLE online for certain changes

…row in set (0.00 sec) mysql> INSERT INTO `huge_table` (text) VALUES (‘test’); …use the documented method for that. What I’m surprised about is that changing a comment does not to require table to be rebuilt, while things like removing auto_increment or changing a default value