On Friday, April 12, 2013 7:43:32 AM UTC-6, Lauri Savolainen wrote:
>
> Thank you for the reply,
>
> The field is defined in the Django model as:
> location_description = models.TextField(_('additional route information'),
> blank=True)
>
> Data length for the corresponding column in the database seems to be 4000
> and the type is NCLOB. The database is created by Django's syncdb and is
> not a legacy one.
>
> This is the raw SQL query the Django admin interface produces:
>
> SELECT DISTINCT "app_route"."id",
> "app_route"."route_no",
> "app_route"."owner_no",
> "app_route"."municipality_code",
> "app_route"."location_description",
> "app_route"."latitude",
> "app_route"."longitude"
> FROM "app_route"
> inner join "app_observationevent"
> ON ( "app_route"."id" =
> "app_observationevent"."route_id" )
> WHERE "app_observationevent"."observation_date" >= :arg0
> ORDER BY "app_route"."id" DESC
>
> Executing it via the Django management shell django.db.connection produces
> the same error (ORA-00932: inconsistent datatypes: expected - got NCLOB)
> but when I remove the "app_route"."location_description" field from the
> SELECT projection the query executes successfully.
>
>
Yes, this is caused by the use of a SELECT DISTINCT over a LOB column,
which Oracle does not allow. The DISTINCT was added to admin queries over
joined fields as a result of ticket #15819. As for workarounds -- I'm
afraid I don't have any suggestions for you.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
