On Friday 06 August 2010, you wrote:
> By the way, have you tried the "full text search" of the Koo (KDE
> OpenObject) client? It uses the Postgres text indexing capabilities
> (nothing we should use on every field, but useful for partner names), so
> if you search for "Lopez" it will match both "López" and "Lopez", but
> also if you search for "Eléctricos" (plural) it will match "eléctrico"
> (singular)...
Interesting
> Maybe we should allow (from the framework side) to specify that a
> (text/char) field should be indexed like that (maybe something like
> "field.char('Name', size=128, human_search=True)"). And the OpenERP
> clients should be nice enough to use such 'human' search by default for
> this fields (otherwise the standard exact search should be used).
Yes, I was thinking of a field attribute (like the "human_search" you say),
too.
On Friday 06 August 2010, you wrote:
> By the way, have you tried the "full text search" of the Koo (KDE
> OpenObject) client? It uses the Postgres text indexing capabilities
> (nothing we should use on every field, but useful for partner names), so
> if you search for "Lopez" it will match both "López" and "Lopez", but
> also if you search for "Eléctricos" (plural) it will match "eléctrico"
> (singular)...
Interesting
> Maybe we should allow (from the framework side) to specify that a True)") . And the OpenERP
> (text/char) field should be indexed like that (maybe something like
> "field.char('Name', size=128, human_search=
> clients should be nice enough to use such 'human' search by default for
> this fields (otherwise the standard exact search should be used).
Yes, I was thinking of a field attribute (like the "human_search" you say),
too.