On 12 jun, 21:37, "Leo Soto M." <[EMAIL PROTECTED]> wrote: > On Thu, Jun 12, 2008 at 8:35 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > [...] > > > Since then I've opened ticket [2]#7420 with a patch > > I see that part of the patch deals with the fact that the underlying > adapter prefer to receive actual date and time instances for date and > time parameters, instead of strings. I have the same problem when > talking to JDBC drivers. > > To solve it I proposed[1] another strategy: delegate type conversion > to the backend.
OK, I have filled #7560 with a patch which delegates date, time, datetime and decimal python -> db conversion to the database backend. It also ensures that for basic field types (IntegerField, BooleanField, ...) the backend will receive the "expected" basic python type (int, bool, ...). http://code.djangoproject.com/ticket/7560 This should help other external-backend mantainers. -- Leo Soto M. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
