On 12/02/2011, at 4:15 AM, Jan Provaznik wrote:
If I remember correctly this is because removing and then adding column (which Josef told is only way for postgres DB), which drops cloud_account for instance, but not sure, maybe Josef can comment this more. Unfortunately I tested it on new DB :(
From hazy memory of how PG operates, could this be from referential integrity constraints on the tables? If so, maybe it's possible to defer the constraint until after the column has been changed, and hopefully avoid cloud_account being dropped?