Accidentally putting a foreign key between an InnoDB table and a MyISAM table results in an error "Cannot add or update a child row: a foreign key constraint fails"
My presentations at OSDC 2014 on the Gold Coast!
So some ludicrous proportion of SQL these days is generated by one ORM or another. And all the cool kids have decided to move on to the next thing anyway. So that got me thinking ... when we talk to an SQL database through an ORM, we're turning a bunch of operations on objects into a human readable query language, then turning that back into a query plan. *Why?*
A (somewhat sketchy) connector between HTTP and postgres stored procedures ...