... Replying to my own post on this bit... of course the older Django 1.1.x can still be used with the older PostgreSQL 7 without hitting this issue regardless as I'm assuming the patch for #8901 isn't being applied back to the 1.1 series :). Perhaps worth being explicit in the Django documentation for 1.2 about which PostgreSQL version is required as a minimum (both for the benefit of users and also for anyone submitting patches to the PostgreSQL back-end so they know what they have to work with!).
> Russ - I guess the choice is either a note in the Django docs/release > notes about this issue and suggesting anyone on 7 adds in > pg_get_serial_sequence as per the above link (if that does indeed > work) or alternatively change the code touched by #8901 such that it > only adds the calls to pg_get_serial_sequence for version 8 onwards > and for version 7 it either reverts to guessing the sequence name as > it used to (with a caveat in the documentation that for long model or > field names there will be the errors that #8901 fixes) or > alternatively it calls the SQL listed in the above pgfoundry link to > fish out the sequence names itself (it could call that sql always > regardless of postgresql version but I guess there's a tiny risk that > in a later version of postgresql the catalog structure could change so > calling pg_get_serial_sequence is preferred when it's available). -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
