Issue 58 in django-evolution: Adding a Boolean field causes problems with PostgreSQL

[codesite...@google.com]

Comment #14 on issue 58 by AdrianElford: Adding a Boolean field causes
problems with PostgreSQL
http://code.google.com/p/django-evolution/issues/detail?id=58

I managed to clear up the ...'pending trigger events' problem by copying
the sql output
of evolve --sql, creating an sql mutation and adding SET CONSTRAINTS ALL
IMMEDIATE;
to the first line. I'm a evolution/postgres n00b so can anyone explain why
this is/isn't a
good idea?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings