If the X-Men existed in medieval times, would they be casted as demons or witches? Or perhaps some of them would be worshiped as magical beings? Would a leader emerge amongst them? Illustrator Nate Hallinan explored the idea, which resulted in ‘The Order of X’. This is a personal fan-fiction variation on the X-Men. I thought it would be a fun exercise to do the X-Men in an alternate medieval/fantasy reality. Prejudice and discrimination were rampant in our history. Being a darker and less civilized time, fear and hatred ran deeper making it an interesting setting for the X-Men. The…
Read the full article: If The X-Men Lived In Medieval Times
via MakeUseOf If The X-Men Lived In Medieval Times
common_schema 2.2 is released. This is shortly after the 2.1 release; it was only meant as bug fixes release but some interesting things came up, leading to new functionality.
Highlights of the 2.2 release:
Better QueryScript isolation & cleanup: isolation improved across replication topology, cleanup done even on error
Added TokuDB related views
split with “index” hint (Ike, this is for you)
table_rotate(): a logrotate-like mechanism for tables
Better QueryScript isolation & cleanup
common_schema 2.1 introduced persistent tables for QueryScript. This also introduced the problem of isolating concurrent scripts, all reading from and writing to shared tables. In 2.1 isolation was based on session id. However although unique per machine, collisions were possible across replication topology: a script could be issued on master, another on slave (I have such use cases) and both use same (local) session id.
With 2.2 isolation is based on server_id & session id combination; this is unique across a replication topology.
Until 2.1, QueryScript used temporary tables. This meant any error would just break the script, and the tables were left (isolated as they were, and auto-destroyed in time). With persistent tables a script throwing an error meant legacy code piling up. With common_schema 2.2 and on MySQL >= 5.5 all exceptions are caught, cleanup is made, leaving exceptions to be RESIGNALled.
A couple TokuDB related views help out in converting to TokuDB and in figuring out tables status on disk:
sql_alter_table_tokudb will help you out to generate the complex ALTER statement to TokuDB engine if you happen to used COMPRESSED InnoDB tables with KEY_BLOCK_SIZE specified. The view generates a complex DROP KEYs & ADD KEYs statementl this is due to bug …
tokudb_file_map simplifies the INFORMATION_SCHEMA.Tokudb_file_map table: the original view is not normalized and is difficult to interpret and follow when your table had many indexes or is partitioned (I will write more on this shortly). with common_schema’s tokudb_file_map you get, per table, the list of files representing that table, along with a couple Shell commands to tell you the thing you want to know most: “what is the size of my TokuDB table on disk?”
QueryScript’s split device now supports the “index” parameter (or hint), which instructs the split() operation to use an explicitly named index. If used, the index must exist and must be UNIQUE.
Rotate your tables a-la logrotate with table_rotate(): generate a new, identical, empty table, version your table, pushing older versions along the line; optionally drop older versions. You get the picture. Got some nice use case behind this on cleaning up a test database.
On MySQL >= 5.5 throw() uses SIGNAL. No more weird “table `Unknown column ‘$t’ in ‘field list’` does not exist” messages. Just plain old:
ERROR 1054 (42S22): Unknown column ‘$t’ in ‘field list’
common_schema is free and open source. It is licensed under GPL v2. This is where you can find and download latest common_schema release.
Your input is welcome! Please submit your bugs, or otherwise share your experience with common_schema.
via Planet MySQL common_schema 2.2: better QueryScript isolation & cleanup; TokuDB; table_rotate, split params