On Ruby on Rails with PostgreSQL, and Acts as Paranoid

September 25, 2007 by kigster

This post has moved:

Posted in Ruby on Rails, Technology | 4 Comments

on October 11, 2007 at 5:03 am anonymous coward

Thanks; I didn’t know you could add additional db constraints in migrations. Your partial index is also way cool.

I agree re: using database-defined constraints: the database handles this more efficiently and complete than Rails; why not let the db handle this?

I know this is not the Rails philosophy at this time, but I think David’s philosophy might change once MySQL catches up w/ modern ODBMS features.
on October 11, 2007 at 11:45 am kigster

Thanks!

I believe MySQL now supports foreign keys, in fact the syntax shown here should work as is for mysql too. Not the check constraints though.
on November 2, 2007 at 12:20 pm Database Constraints, Stereotypes Rails, Culture, Talmud, Gender, MINASWAN, Religion. But ABSOLUTELY NO BONDAGE PLAY | thirdbIT

[...] p. 324). Mostly what I found on the web about rails and foreign key constraints was a bunch of people talking about how they do use them and you’d be crazy and irresponsible not to. Yes, [...]
on June 4, 2008 at 7:35 am ruby sql indexes

[...] with ruby on Rails project. Covers foreign key constraints, check constraints and partial indexes.http://tektastic.wordpress.com/2007/09/25/on-ruby-on-rails-with-postgresql-and-acts-as-paranoid/firstworks Programming with SQL Relay using the Ruby APIProgramming with sql Relay using the ruby [...]