> Item.objects.dates('created', 'day')[0]
> DatabaseError: ORA-00923: FROM keyword not found where expected
That's the exact error that's giving me problems -- I think it's one
of the same issue as I'm having. It's because of the `col.rsplit('.',
1)[1]` logic in Oracle's `as_sql` when doing offsets. In other words
when the column is wrapped in a function (like the datetime SQL is)
then there will be a parenthesis after the quote still in the column
name.
> Did GeoDjango break in r8426 then, as Oracle in general did? That's
> where extra_select changed. I can see how our new code in r8445
> breaks on your function column.
Yes, GeoDjango broke in 8426, but a simple fix was committed in 8431
that fixed it PostGIS and MySQL -- basically I just needed to make
compatible for the data structure changes.
I came to the same conclusion on the pickling problems being caused by
the fact that OracleQuery doesn't exist at the module level, but
rather is returned from a function call dynamically.
-Justin
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
