On Wednesday, October 6, 2010, Tom Eastman <[email protected]> wrote: > Hey guys, > > I'm using Django to create an interface for a legacy PostgresQL database. > The primary keys for my tables use sequences that aren't named the way django > expects them to be (i.e. '<table>_<column>_seq'), this means I can't call > them AutoFields. > > Essentially, my problem is identical to that described by > > > http://stackoverflow.com/questions/2516176/django-postgres-how-to-specify-sequence-for-a-field > > > and > > > http://code.djangoproject.com/ticket/1946 > > > There appear to be three or so half-finished proposed solutions to this > issue. I definitely need to find a way to make this work, and I would > greatly appreciate any guidance on what might be the best way to solve this > problem. If we can find a way to solve it for *everyone* that would be even > better. > > Any thoughts or suggestions?
Yes - questions of usage and requests for design guidance should be directed to Django-users. Unless you have a specific suggestion for how to move ticket #1946 forward, this isn't a topic for django-developers. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
