Re: magic_removal table update

2006-01-25 Thread Max Battcher
Jason Davies wrote: ALTER TABLE auth_groups ALTER id SET DEFAULT nextval('public.auth_group_id_seq'::text); This was the peculiar incantation I was looking for, thanks. Now I just have a non-fatal, non-blocking error from the django_content_types table... -- --Max Battcher--

Re: magic_removal table update

2006-01-25 Thread Adrian Holovaty
On 1/25/06, Max Battcher <[EMAIL PROTECTED]> wrote: > I'm living on the bleeding edge (just migrated to rev. 2123) with my > current development, and followed the suggested ALTER TABLE commands > from the wiki page, and though I can read from the data (all of the > views work correctly), I can't

Re: magic_removal table update

2006-01-25 Thread Jason Davies
Max Battcher wrote: > I'm living on the bleeding edge (just migrated to rev. 2123) with my > current development, and followed the suggested ALTER TABLE commands > from the wiki page, and though I can read from the data (all of the > views work correctly), I can't save because all of the

Re: magic_removal table update

2006-01-25 Thread Andreas Stuhlmüller
On 1/25/06, Max Battcher <[EMAIL PROTECTED]> wrote: > At this point I'm a bit stumped on how to properly do this. Is there an > easy way to resync the sequences in PostgreSQL that I've overlooked? Did you try "django-admin.py sqlsequencereset"? This used to work for me. Andreas

magic_removal table update

2006-01-25 Thread Max Battcher
I'm living on the bleeding edge (just migrated to rev. 2123) with my current development, and followed the suggested ALTER TABLE commands from the wiki page, and though I can read from the data (all of the views work correctly), I can't save because all of the sequences are now out of sync.