… with TokuDB, of course I wanted to compare InnoDB performance vs TokuDB. I have a particular workload I’m interested in…, and the table looks like: CREATE TABLE sbtest$I ( id BIGINT UNSIGNED NOT NULL, k INTEGER UNSIGNED DEFAULT ’0′ NOT NULL…` int(10) unsigned NOT NULL DEFAULT ’0′, `mid` int(10) unsigned NOT NULL DEFAULT ’0′, `id` bigint(20) unsigned NOT NULL, `k` int(10…
Post: PHP vs. BIGINT vs. float conversion caveat
January 10, 2008 By 27 Comments
…-bit identifiers are not enough and you have to use BIGINT 64-bit ids; e.g. if you are encoding additional… as float (especially on 32-bit systems where 32-bit int overflow will implicitly convert to float) and getting strange bugs… numeric value handling: it can be used to workaround signed vs. unsigned int issues; it helps with float formatting; always a saviour…
Comment: COUNT(*) for Innodb Tables
December 20, 2011 By 32 Comments
… | Type | Null | Key | Default | Extra | +—————+————–+——+—–+———+—————-+ | id | bigint(20) | NO | PRI | NULL | auto_increment | | id_acct | int(11) | NO | MUL | 0 | | mysql> select… if it’s due to the difference in field type (bigint vs int).
Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark
March 11, 2013 By 7 Comments
… id=”attachment_13599″ align=”alignright” width=”210″] MySQL 5.6 vs MySQL 5.5 & the Star Schema Benchmark[/caption] So far…_OrderKey bigint not null, LO_LineNumber tinyint not null, LO_CustKey int not null, LO_PartKey int not null, LO_SuppKey int not null, LO_OrderDateKey int not null, LO_OrderPriority…
