Just a question - how, if at all, is aggregation going to be supported or worked around on custom field types?
On Jan 6, 8:14 am, "Ian Kelly" <ian.g.ke...@gmail.com> wrote: > On Mon, Jan 5, 2009 at 9:21 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: > > The one's that are a result of Oracle not returning a Decimal can be solved > > be inserting "..." before and after the number, in placeess of explicitly > > saying Decimal(unless of course this is actually a typecasting issue in > > Django itself, in which case that should be fixed) this is done a few other > > places in aggregates regress. > > The Decimal conversion might fail to happen if the corresponding field > passed to resolve_columns is not a DecimalField. This happens for > instance when using extra selects, where no field object is available. > My guess is that the fields for the aggregate columns are getting > excluded or misaligned somehow. This could also be the cause of the > datetime/time issue. > > > The SQL command not properly ended appears to be the result of an annotate > > call followed by a call to aggregate(). I don't have a clue what causes > > that as I've used Oracle in my life :) . > > I'll take a look at the queries tomorrow and see if I can straighten them out. > > Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
