Are there any consequences for renaming sequences to match the tables
which own them?
In an existing production Django project I have just converted auth.user
into common.user and company.userprofile into common.userprofile.
Having gone through the migration process more or less unscathed the
original sequences are owned by the renamed tables. Eg
public.auth_user_id_seq is owned by public.common_user.id
Everything seems to work fine but my unit tests are playing up and error
messages are showing the original (and still correct) sequence names. It
would make much visual sense to me now and especially to the future me
(or anyone else) if the sequences were renamed as well.
I know how I could do it but I just need to know if I should.
Thanks for any advice
Mike
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/f0711339-6268-7894-2480-ead979282422%40dewhirst.com.au.
