All my bug reports get classified as spam, so please accept this via email.
There's a bug with the order_with_respect_to in that it uses count(*) to determine the value of _order, this works well until you delete more than one object from the middle of the list... in which case a new item which should be at the end isn't. A more correct approach would be to check what the current highest _order value is and increment it. eg. SELECT _order+1 FROM %s WHERE %s = %%s order by _order desc limit 1 I've tested it with mysql using the patch (modified to include the above sql) from http://code.djangoproject.com/ticket/1760 (incidentally, any chance we can have that patch incorporated into django?) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
