[stormyfacts] The code doesn't enforce foreign keys in Sqlite

Bug #990919 reported by m4v on 2012-04-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu IRC Bots
Low
Unassigned

Bug Description

So until now I have been working thinking that SQLite and MySQL were enforcing foreign keys, but it turns out they weren't. "PRAGMA foreign_keys = ON" doesn't work with storm (https://bugs.launchpad.net/storm/+bug/676702) and apparently I was using MyISAM with my MySQL server.

The result is that the code can't even create a table without upsetting the constraint rules, if you're using InnoDB with MySQL then you aren't going to go far with Stormyfacts.

m4v (m4v) on 2012-04-30
summary: - [stormyfacts] MySQL support is fubar in Precise
+ [stormyfacts] MySQL fails with InnoDB engine
summary: - [stormyfacts] MySQL fails with InnoDB engine
+ [stormyfacts] The code doesn't enforce foreign keys anywhere
Changed in ubuntu-bots:
importance: High → Medium
m4v (m4v) on 2012-04-30
Changed in ubuntu-bots:
status: Confirmed → Triaged
description: updated
description: updated

for now I disabled foreign keys, at least this way MySQL will work regardless of the engine.

m4v (m4v) wrote :

fixed foreign keys and now work with MySQL, Sqlite will have to go without foreign keys, due to that bug in Storm.

Changed in ubuntu-bots:
importance: Medium → Low
summary: - [stormyfacts] The code doesn't enforce foreign keys anywhere
+ [stormyfacts] The code doesn't enforce foreign keys in Sqlite
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers