Ruby on Rails | Screencasts | Download | Documentation | Weblog | Community | Source

Ticket #3909 (closed enhancement: untested)

Opened 2 years ago

Last modified 1 year ago

ACID migrations for databases which support it.

Reported by: nzkoz Assigned to: nzkoz
Priority: normal Milestone: 1.2.4
Component: ActiveRecord Version: 1.0.0
Severity: normal Keywords:
Cc: tarmo

Description

Postgres and SQL server support transactional DDL, migrations should use BEGIN/COMMIT where possible.

For databases which support it, this makes migrations much more reliable. However it's important that this doesn't break the other databases.

Change History

02/21/06 01:13:12 changed by nzkoz

  • owner changed from David to nzkoz.
  • status changed from new to assigned.

02/26/06 19:14:54 changed by anonymous

  • keywords set to fd.

03/03/06 02:37:52 changed by esad@esse.at

See http://www.ruby-forum.com/topic/56355 What do you think?

03/25/06 21:56:06 changed by david

  • keywords deleted.
  • severity changed from major to normal.

05/23/07 20:11:45 changed by josh

  • status changed from assigned to closed.
  • resolution set to untested.

Koz! Your a core member now, you should know that you need patches and a test case. :)

08/23/07 22:07:35 changed by tarmo

  • cc set to tarmo.

There's a simple plugin (no tests though) that makes migratsions transactional. It works well on at least postgresql 8.

http://www.redhillonrails.org/#transactional_migrations

The implementation is quite naive though, it does not attempt to make sure that the database actually supports transactional DDL.