Re: PostgreSQL, migrations and "because it has pending trigger events"
Re: PostgreSQL, migrations and "because it has pending trigger events"
- Subject: Re: PostgreSQL, migrations and "because it has pending trigger events"
- From: Henrique Prange <email@hidden>
- Date: Tue, 23 Oct 2012 11:13:23 -0200
Hi Pascal,
I've seen this problem in other scenarios too. Adding the following statement at the beginning of the migration solved it:
ERXJDBCUtilities.executeUpdate(channel, "SET CONSTRAINTS ALL IMMEDIATE;");
Cheers,
Henrique
On 23/10/2012, at 10:13, Pascal Robert <email@hidden> wrote:
> FYI, if you are using migrations and PostgreSQL, and you are getting "ALTER TABLE table name failed because it has pending trigger events", it's because you are adding a boolean column without setting the default value. I got this problem this morning because I didn't add the default value for one of the 3 boolean columns I was adding in the migration.
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden