auto_migrate! blows up on sqlite3 if dm-constraints are enabled
Reported by Martin Gamsjaeger (snusnu) | May 24th, 2009 @ 01:06 AM | in 0.10.0
I get the error at
if I try to run auto_migrate! on a sqlite3 db, when dm-constraints are required. without dm-constraints, everything migrates nice.
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) June 16th, 2009 @ 05:16 PM
This error still happens. The stacktrace changed though: new one at http://pastie.org/514369
-
Dan Kubb (dkubb) June 16th, 2009 @ 10:37 PM
- Assigned user set to “Dan Kubb (dkubb)”
- State changed from “unconfirmed” to “accepted”
- Milestone set to “0.10.0”
-
Dan Kubb (dkubb) June 30th, 2009 @ 12:32 AM
- State changed from “accepted” to “resolved”
(from [add40d7b8c2c7d4f69e0065ddcfac7193b795e65]) [dm-constraints] Updated to not explode when dm-constraints used with SQLite3
- For now foreign key DDL statements are ignored, but in future implementations CHECK constraints may be used to simulate foreign keys, until native support is added to SQLite3
[#863 state:resolved] http://github.com/datamapper/dm-more/commit/add40d7b8c2c7d4f69e0065...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
People watching this ticket
Dan Kubb (dkubb)
Martin Gamsjaeger (snusnu)
Referenced by
-
839
[dm-constraints] should default to :constraint => :protect
Also, #864 which was related is now invalid. #863 (also
r...
-
863
auto_migrate! blows up on sqlite3 if dm-constraints are enabled
[#863 state:resolved]
http://github.com/datamapper/dm-mo...