Ruby + Postgres = Bad Idea or Good Idea?

rubyonrails-talk
1

I much prefer PostgreSQL over MySQL. MySQL's interpretation of the SQL standard(s) has driven me up the wall at times. Does it still force a default value on every column with a NOT NULL constraint?

PostgreSQL works great with Rails, the support in the core is exactly as for MySQL. I've encountered the odd extension (plugin, gem, whatever) that only supports MySQL, but that may rather an indication of the extension's quality.

Michael

2

Some other points you might want to check if you compare these two:

- Behavior under concurrent accesses: Transactional isolation, locking. - Transactional changes to the DB structure. - Performance with many joins. - Changing the structure of (large) existing tables.

In my experience, PostgreSQL is better in all of these.

Michael

3

"Some other points you might want to check if you compare these two:

  • Behavior under concurrent accesses: Transactional isolation, locking.
  • Transactional changes to the DB structure.
  • Performance with many joins.
  • Changing the structure of (large) existing tables.

In my experience, PostgreSQL is better in all of these."

Me too.