> Weird, I'm not sure why 1.3.7 vs 1.3.6 would make a difference, and I'm > pretty sure I was testing on 1.3.7.
I've tried dropping down to just sqlite3, but haven't been able to trigger it there. Regexps are fragile, but I don't think that's the problem. Here's the code I'm using: https://gist.github.com/4633137 Here's the output I get: Using SQLite3 1.3.6 SQLite3::ConstraintException: column email is not unique Sequel::UniqueConstraintViolation Using SQLite3 1.3.7 SQLite3::ConstraintException: constraint failed Sequel::CheckConstraintViolation With sequel 3.43.0 both are raising Sequel::DatabaseError as expected with the same error messages as above i.e. "column email is not unique" and "constraint failed". Can anyone else reproduce this? Cheers, Tim -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
