With JSON functionality, alternate protocols (HTTP, memcache), a move towards saner defaults and crash safety, pluggable logging etc it really looks like MySQL is following what we did in Drizzle years ago, which is great!
Ramblings
Ramblings which occasionally resemble reality. This is the blog of Stewart Smith.
MySQL-next = Drizzle 5 years ago? http://t.co/v1dgHR9dHO
New #mysql planet post : MySQL-next = Drizzle 5 years ago? http://t.co/iDFY4HSHXM
MySQL-next = Drizzle 5 years ago?: With JSON functionality, alternate protocols (HTTP, memcache), a move towar… http://t.co/ZkfNLAfhYZ
MySQL-next = Drizzle 5 years ago?: With JSON functionality, alternate protocols (HTTP, memcache), a move towar… http://t.co/6SDiaRWRRI
MySQL-next = Drizzle 5 years ago? http://t.co/JKtu0SfdGO
#MySQL MySQL-next = Drizzle 5 years ago? – With JSON functionality, alternate protocols (HTTP, memcache), a move t… http://t.co/oRY4XoIs8X
MySQL-next = Drizzle 5 years ago? http://t.co/OrLFU8P458
@stewartsmith HTTP? Queries over http? Updates? Or have I missed the point?
RT @stewartsmith: MySQL-next = Drizzle 5 years ago? http://t.co/v1dgHR9dHO
RT @planetmysql: MySQL-next = Drizzle 5 years ago? http://t.co/JKtu0SfdGO