On Tue, Jan 6, 2009 at 11:16 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: > The datetime issue looks like it's just an issue of porting this logic: > http://code.djangoproject.com/browser/django/trunk/django/db/backends/oracle/query.py#L72 > > over to the coerce aggregates function. There's a bit of decimal logic > above, but I don't think it's anything different than what we already have, > is it?
The logic you have identified appears to be the right idea. My only question is whether we should be needing to replicate this logic in the aggregation coercion function - the code you identified is executed as part of resolve_columns, which should be executed as a precursor to aggregate coercion. This means the problem may lie in resolve_columns not resolving enough columns, rather than extra coercion being required. I should be able to take a look at this tonight, unless someone with an actual Oracle install beats me to it. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
