Yes, you are all right. What I wrote applies to MySQL. It hadn't occurred to me that the original poster might be using Postgres. This is a great advantage over MySQL, as I've run into the problem several times when my migration would fail halfway (at least on my development db) and I'd have to monkey around to get things back to normal.
--Andrew On 11 May, 06:14, Stephen Haberman <[EMAIL PROTECTED]> wrote: > On Fri, 11 May 2007 10:30:06 +0200 > > Jonathan Weiss <[EMAIL PROTECTED]> wrote: > > This does not work in MySQL: > > > BEGIN; > > ALTER TABLE ..... > > UPDATE TABLE ... > > ALTER TABLE .... > > COMMIT; > > > This will not be rolled back correctly. > > Interesting. > > In PostgreSQL it works just fine. > > Begin, alter add column, rollback. Then a select, no new column. > > Begin, alter add column, commit. Then a select, there is the new column. > > - Stephen --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
