The fix in #8901 partially fixes #1946, making it easier to use django with some egacy postgres databases. It does not however aid in the use of legacy databases that uses postgres' own inheritance as pg_get_serial_sequence() doesn't work on these. Until postgres gets its act together :) we can add a function to postgres itself that looks up the sequence names in more cases than what pg_get_serial_sequence() can handle.
Since this might be the first time this particular type of solution has been suggested the core devs need to have a think about whether it is at all desirable. HM -- 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.
