On Sun, Oct 12, 2008 at 4:25 PM, Daniel Roseman <
[EMAIL PROTECTED]> wrote:
> On Oct 12, 8:46 pm, dbee <[EMAIL PROTECTED]> wrote:
> > ### ERROR 2 ###
> <snip>
> > Exception Type: ProgrammingError at /blog/venture-capital-pitfalls/
> > Exception Value: ERROR: operator does not exist: character varying =
> > integer
> > LINE 1: ...M "tarait1_blog" WHERE ("tarait1_blog"."category" = 0 AND
> > "...
> > ^
> > HINT: No operator matches the given name and argument type(s). You
> > might need to add explicit type casts.
> >
> > SELECT COUNT(*) FROM "tarait1_blog" WHERE ("tarait1_blog"."category" =
> > 0 AND "tarait1_blog"."active" = True )
>
>
> This sounds like a difference in the way your database is set up. Are
> you sure you have the same table definitions, collations, charsets,
> etc?
Or possibly a change to PostgreSQL 8.3 from something earlier. This could
be the result of the change "Non-character data types are no longer
automatically cast to TEXT" described here:
http://www.postgresql.org/docs/8.3/static/release-8-3.html
This was "fixed" (by Django code automatically adding a cast) for
search-type lookups (like, contains, etc.) per this ticket:
http://code.djangoproject.com/ticket/6523
But that change doesn't affect equal lookups, which is what you are doing.
The SQL shown actually looks like the PostgreSQL change may be exposing a
latent bug in your code. 'category = 0' rather sounds more like it should
be 'category = ""' or 'category is null'. I'd take a look at the code
causing that SQL to be generated and see if it is really doing what you
intend it to.
Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
