Open GoogleCodeExporter opened 9 years ago
It seems that this issue cannot be reproduced when using MySQL InnoDB tables,
since they directly support SQL cascading clauses. InnoDB is used by default
on MySQL >= 5.5 (which can be found on the distribution we mainly support:
Ubuntu 12.04).
I tried to revise the SQLAlchemy cascading options in order to better handle
cascading on MyISAM tables (which are still used by default on MySQL 5.1.66,
found on your CentOS 6). However, I had no luck so far.
I think that I will add some hack to force InnoDB tables when the NotreDAM SQL
schema is created. Stay tuned for updates.
BTW: what version of SQLAlchemy are you using?
Original comment by alce...@crs4.it
on 9 Jul 2013 at 3:27
I was using SQLAlchemy==0.8.0b2
Just updated to SQLAlchemy==0.8.2 and still have the same problem. You are
right that the tables are MyISAM and not InnoDB.
Also, I tried altering the tables to InnoDB, but that did not help. I'm sure
its because the foreign key constraints don't exist still. So I'm guessing the
best way would be to dumpdata, drop the tables, set the default storage engine
(https://docs.djangoproject.com/en/1.5/ref/databases/#creating-your-tables),
syncdb then loaddata?
Original comment by jonat...@metaltoad.com
on 10 Jul 2013 at 4:09
Original issue reported on code.google.com by
jonat...@metaltoad.com
on 10 May 2013 at 7:34