I have already given some of my thoughts on django-users and on the ticket for 8901... Andrew Godwin's reasoning above feels sound to me, so considering that and that 1.1 would still work for postgres 7.4 users (plus my desire to see the bug in 8901 fixed sooner rather than later as it does affect me, although I can patch django myself if I have to wait to 1.3 so that's only minor) I'd say...
+1 on option 3 +0 on option 2 -1 on option 1 I think if the fix for 8901 isn't put into 1.2 (i.e. option 2 is chosen) it might be worth adding a note into release notes for 1.2 about it being a known issue just because the change in m2m saves means that users (like me) who have a combination of a longish model name and a longish m2m field name will find things break on upgrading from 1.1 to 1.2 so you'd want to warn them off doing so! Matt -- 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.
