> Can we figure out what this thread is about, and stick to it, please?
As the person who originally started the thread ;-) I'd like to agree a design for a patch which will be accepted into Django trunk and will enable us to close the #3460 ticket. The current #3460 patch needs more work. I've proposed a route forward http://groups.google.com/group/django-developers/msg/48500109ac5e514d and I'd much appreciate people (especially Malcolm, Jack, Collin, but others welcome too) replying to that message with their comments. There is an interesting side-discussion between Ivan/me/Jack/Michael, about whether the underlying Postgresql change actually improves performance. It would be great if someone can provide a simple test case demonstrating that it does. However, that's not the only reason to want the patch, so we should work towards a final patch anyway, and can benchmark that (on the test suite, say) once it's ready for check in. Cheers, Richard. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
