Hi,
Turns out it's not really a Djapian issue, it's related to Django
1.2.1, and the new " 'postgresql_psycopg2" I think.
I've posted about it on "Django users" (
http://bit.ly/b9plZx)
What I was after was the ability to retrieve all comments associated
with a blog entry so that Djapian could index it.
Found a solution that seems to work.
See:
http://bit.ly/b9plZx
Thanks,
R
On Jul 14, 12:17 am, Alex Koshelev <
daeva...@gmail.com> wrote:
> Hi!
>
> Current trunk is the future 2.4 release. Try to checkout the code and run
> indexer. If it will fail again -- post a bug with complete description of
> your problem with code snippets.
>
> ---
> Alexander Koshelev
>
>
>
> On Tue, Jul 13, 2010 at 2:57 PM, rd-london <
roland.d...@gmail.com> wrote:
> > Hi,
> > Having issues with Django 1.2.1, if I try to "index --rebuild" get
> > long error stack that includes:
>
> > "
> > django.db.utils.DatabaseError: operator does not exist: text = integer
> > HINT: No operator matches the given name and argument type(s). You
> > might need to add explicit type casts.
> > "
>
> > Home page ofhttp://
code.google.com/p/djapian/says need a >=2.4
> > release to be compliant with Django 1.2.1. But where is that release?
>
> > Downloading latest source fromhttp://
djapian.googlecode.com/svn/trunk/,
> > and setup.py says it is still ver 2.3.
> > So ... any suggestions?
>
> > I haven't tried the latest source, but if that should solve the
> > problem, is Xapian 1.2 strictly necessary or can I go stay with 1.0.7?
>
> > Thanks,
> > R
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Djapian Users" group.
> > To post to this group, send email to
djapia...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
djapian-user...@googlegroups.com<djapian-users%2Bunsubscribe@goog
legroups.com>
> > .