Re: AutoFields, legacy databases and non-standard sequence names.
On 06/10/10 16:02, Russell Keith-Magee wrote: 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. Sorry, I should have been more clear. What I'm trying to do is solicit suggestions from django developers as to how I *can* move ticket #1946 forward. I can find a way to work around it in my own project, but it would be ideal to solve it on the Django side, for everybody. I mentioned there were three possible suggestions in the ticket discussion as to how to solve the problem. If a Django developer can give me some guidance as to what approach seems to be the best long-term solution, I'm happy to try my hand at writing a patch that can hopefully be incorporated into the codebase. Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
AutoFields, legacy databases and non-standard sequence names.
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. '__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? Cheers, Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
