Re: Backwards incompatibility with fancy PostgreSQL queries and QS-RF

2008-05-01 Thread offspinner
I think I posted a similar issue almost simultaneously with Barry here. This affects MySQL 5.0.41 too. See my post: http://groups.google.com/group/django-users/browse_frm/thread/831667d32f01f5d2 On May 1, 5:59 am, Barry Pederson <[EMAIL PROTECTED]> wrote: > On Apr 30, 11:52 pm, "James Bennett"

Re: Backwards incompatibility with fancy PostgreSQL queries and QS-RF

2008-04-30 Thread Barry Pederson
On Apr 30, 11:52 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On Wed, Apr 30, 2008 at 11:43 PM, Barry Pederson > > <[EMAIL PROTECTED]> wrote: > >  any thoughts on the best way to do this now with QS-RF? > > Well, the official database API docs say [1]: > > "In some rare cases, you might

Re: Backwards incompatibility with fancy PostgreSQL queries and QS-RF

2008-04-30 Thread James Bennett
On Wed, Apr 30, 2008 at 11:43 PM, Barry Pederson <[EMAIL PROTECTED]> wrote: > any thoughts on the best way to do this now with QS-RF? Well, the official database API docs say [1]: "In some rare cases, you might wish to pass parameters to the SQL fragments in extra(select=...)`. For this

Backwards incompatibility with fancy PostgreSQL queries and QS-RF

2008-04-30 Thread Barry Pederson
Using PostgreSQL 8.3 and fulltext indexing, before QS-RF I was able to execute queries like: - q = 'hello world' queryset = Entry.objects.extra( select={ 'snippet': "ts_headline(body, query)", 'rank': "ts_rank_cd(body_tsv, query, 32)", },