On Sep 30, 12:29 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > I've been thinking through, with a couple of different people, how we > can support extra lookup types on fields and so I'm going to reserve > judgement on this particular implementation until I have some thoughts > in order on the latter subject. Maybe you'll convince another maintainer > in the interim, but it's probably a good start to get the patch up to > date and then drop it into the 1.1 features list, since running, tested > code is always a good start for assessing something.
It'd be great to have some sort of drop-in architecture to allow new query types that can be defined perhaps by an installed application, rather than having to modify the Django distribution. That said, since such a beast doesn't currently exist, I've just updated my code to work on a current SVN checkout of Django. From my POV the only thing missing is testing on Oracle, although I appreciate that other viewpoints may see it wildly differently :) > If you're writing an API for talking to the data storage layer, pick a > value for the first day that is consistent at the Django level.... Don't > create extra problems for yourself here by inentionally letting > presentation information leak into the ORM layer. Good point - the code currently attached to the ticket will always force Sunday=1, Saturday=7. This happens regardless of the database backend in use. Thanks for your feedback Malcolm, I'll leave it here for the moment to see what comments other contributors may have. Regards, Ross --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
