The calls to pg_get_serial_sequence were added in to fix #8901 and I noted on that issue that the call wasn't available on PostgreSQL prior to 8, that Django made no claims about which PostgreSQL version it requires as a minimum, but that version 7 was rather old these days with version 8 having been around for 5 years now.
Note that I think it is possible to create pg_get_serial_sequence for PostgreSQL 7: http://pgfoundry.org/tracker/index.php?func=detail&aid=1000463&group_id=1000151&atid=616 (perhaps you could test that Federico?) As noted above, Version 8 was first released in 2005. Version 7.4 has still had bug fixes by the PostgreSQL community to date however to quote from the release notes "The PostgreSQL community will stop releasing updates for the 7.4.X release series in July 2010. Users are encouraged to update to a newer release branch soon. " 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). On Jun 9, 11:27 am, Federico Capoano <nemesis.des...@libero.it> wrote: > I have PostgreSQL version 7.4.27 on my server. The reason for which I > use this version is that is the latest version available for webmin > and my VPS use it. > What can I do? > > I checked the release notes and I didn't notice anything about this > bit. Before upgrading to the last revision I had probably the trunk > equivalent to the just released 1.2 > > Thanks for your help. -- 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.
