El Miércoles, 11 de Febrero de 2009, Matt Amos escribió: > > Rails guys: we're using InnoDB tables for a reason, you know. > > yes - for transactions. the foreign keys are a plus, but they can't do > all the checking (relation_members, changeset timeouts, etc...).
For relations: see my reply to Stefan. For changeset timeouts: triggers, triggers, triggers. Or just initialize the closing time of a changeset to a date in the future. > also, it becomes a pain for the client to distinguish between a mysql > error because of an invalid foreign key reference, a mysql error > because of a server code bug and a mysql error because the db server > died or the network went down. Can't Rails check the error number returned by MySQL? -- ---------------------------------- Iván Sánchez Ortega <i...@sanchezortega.es> Q: How many Harvard MBA's does it take to screw in a light bulb? A: Just one. He grasps it firmly and the universe revolves around him.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
