News for hackers. Stuff that matters.
Re:PostgreSQL 9.3 Beta 1 Released by effn on Monday May 13, 2013 @12:37PM (#5699653)
ActiveRecord doesn't even support constraints in the first place.
Re:PostgreSQL 9.3 Beta 1 Released by pjungwir on Monday May 13, 2013 @12:55PM (#5699787)
Shameless plug: here is a gem I wrote to manage foreign keys and CHECK constraints (and also indexes) in a Rails project:

https://github.com/pjungwir/db_leftovers

Re:PostgreSQL 9.3 Beta 1 Released by joevandyk on Monday May 13, 2013 @01:46PM (#5700152)
What do you mean by "support constraints"?

If I, for example, violate a unique index, a ActiveRecord::RecordNotUnique exception is raised.

Re:PostgreSQL 9.3 Beta 1 Released by mjhoy on Monday May 13, 2013 @03:47PM (#5700977)
Is that true? I might be wrong about this, but I think ActiveRecord checks for uniqueness (and other constraints) in application code, generating an extra database query if needed. If you _actually_ violate the unique index, a PGError is raised (if using postgres).
Re:PostgreSQL 9.3 Beta 1 Released by FooBarWidget on Monday May 13, 2013 @04:24PM (#5701158)
No. ActiveRecord checks for constraints on top of what the database offers. You are free to specify database constraints if you like. In older versions of ActiveRecord, uniqueness errors generate a generic database exception. In recent versions, uniqueness errors generate the specific exception RecordNotUnique.