>> I think the attached patch is more correct (I've backpatched it into
>> the 0001 migration because making it a separate migration makes it
>> somewhat destructive -- it's easier to just change it manually on
>> existing installs if you have one)
>
> Thanks! Can it be pushed into the git repository, or does it need testing or something?
>
I understand that changing id fields to AutoFields can be destructive for existing install, but on the other hand, the
currentstate of the repository is problematic as it causes pglister_sync to fail by default.
Another solution could be to add sequences directly in postgres using RunSQL() in a migration to turn these fields into
defacto serial fields. This is a bit hacky, but non-destructive. What do you think?
--
Célestin Matte
