So, our managed implementation of LevelDB is just about ready to go out and socialize. The following tests were done on an HDD, and all include writing a million records (16 bytes key, 100 bytes values) to storage.
It is everywhere in the world of MySQL that if your replication is broken because an event caused a duplicate key or a row was not found and it cannot be updated or deleted, then you can use ‘ STOP SLAVE;SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1;START SLAVE; ’ and be done with it. But what if the statement is part of a multi-statement transaction? Well, then it becomes more interesting ...
Quality and productivity are, of course, important things. I certainly wouldn’t continue to practice Test-Driven Development if it added defects or took a significantly longer time to create functionality. But that’s not why I practice TDD.
A common feature in software systems is to allow users to define their own fields in data structures. Consider an address book - there's a host of things that you might want to add. With new social networks popping up every day, users might want to add a new field for a Bunglr id to their contacts.