> If we'd thought of it, dropping 7.4 support in 1.2 would have been the > right thing to do. However, retroactively doing so now would be abuse > of the time machine privileges and I'd like to avoid being grounded. > #1's not worth the effort, so that just leaves #2, which sounds about > right to me.
Django 1.2 doesn't say which versions of postgresql it supports at the moment - that may well be just be semantics tho' as I guess anyone who's tested it will have found it works so far :). I guess people who are going to hit the bug in #8901 (which may be very few) when changing from 1.1 to 1.2 will discover the problem in testing so can hold off on migrating (or apply the patch manually), whereas people using postgresql 7.4 may already be on version 1.2 and breaking it working on 7.4 in a point release on 1.2.1 would be less acceptable as they would already have moved to 1.2 and couldn't then get security updates for 1.2 [1] [1] Note that on django-users I did mention that it's possible to create the function in postgresql 7.x that exists in 8 which the fix for #8901 relies on, so they have a work around too. -- 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.
