Comments on: Clone My Fields, Please

By: Andrew Pelt

Andrew Pelt — Sat, 06 Mar 2010 20:21:13 +0000

Thanks for your article. I am new at python and this will be a big help.

By: JR

JR — Fri, 14 Nov 2008 00:14:08 +0000

This article and the accompanying comments were most helpful in converting MercuryTide’s search to Django 1.0+ compatibility, thank you!

I ended up using MercuryTide’s search as a starting point, but wrote the actual search aspect myself, because InnoDB doesn’t support MySQL’s fulltext search.

By: Yeago

Yeago — Wed, 14 May 2008 16:54:09 +0000

I think that fixed one issue, Craig.

Now I’m attempting to track down an odd bug whereby attempting to filter() a result-set results in [], regardless of match.

By: Craig Ogg

Craig Ogg — Tue, 29 Apr 2008 00:39:19 +0000

I haven’t checked it to any real extent, but it looks like just bad subclassing form. Adding *args and **kwargs in the usual way should make the problem disappear:

def __init__(self, index_column, *args, **kwargs):
super(SearchManager, self).__init__(*args, **kwargs)

Similarly for SearchQuerySet.

By: Yeago

Yeago — Mon, 28 Apr 2008 18:28:22 +0000

Don’t suppose the SearchManager is choking upon the last svn update?

django/db/models/query.py

line c = klass(model=self.model, query=self.query.clone())

“__init__() got an unexpected keyword argument ‘query’”

Digging around. Letcha know if I find something out.

By: Jason Wadsworth

Jason Wadsworth — Sat, 05 Apr 2008 15:04:04 +0000

Last I checked, the built-in Django support only supported single columns, and only in boolean mode. That’s definitely useful, but it’s not appropriate for every situation.

I looked at my code and remembered the fix for the quote_name problem. The organization of the backends in Django changed in the trunk so that quote_name was accessed through a DatabaseOperations interface.

Replace:
backend.quote_name(...)

With:
ops = backend.DatabaseOperations()
ops.quote_name(...)

By: Yeago

Yeago — Thu, 03 Apr 2008 19:04:55 +0000

Maybe the whole comment was dumb. Sphinx is for MySql+Django only.

By: Yeago

Yeago — Thu, 03 Apr 2008 18:59:10 +0000

Mmm…. ok, I retract the above remark about it being built in. Apparently Django doesn’t provide for full-text across columns.

By: Yeago

Yeago — Thu, 03 Apr 2008 18:25:16 +0000

Actually, I’m going to ignore the stuff at mercurytide as this has since been built-in to Django.

Also, for those non-mysqlers:

http://www.davidcramer.net/code/79/in-depth-django-sphinx-tutorial.html

By: Yeago

Yeago — Thu, 03 Apr 2008 14:49:46 +0000

Yes, mysql.

I’m using Django SVN and I’ve verified that quote_name exists in that class.