<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 9/22/2010 9:22 AM, <a class="moz-txt-link-abbreviated" href="mailto:ceooph+drupallist@gmail.com">ceooph+drupallist@gmail.com</a> wrote:
<blockquote cite="mid:4C9A0309.2020205@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Le 21/09/2010 18:14, Ted a écrit :
<blockquote cite="mid:4C98D9F0.8030609@webfirst.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
Another approach is to use the computed_field module to create a
computed field that stores all the values from the other fields,
then add that field as a filter. It's a hack, but for small
datasets it won't affect performance.<br>
<br>
</blockquote>
It's very helpful. Thank you !!!<br>
</blockquote>
<br>
I forgot to mention the other benefit of this approach: you can
allow searching on multiple orderings of a field, such as names, by
concatenating them together in the computed field: "Last, F. M. %
Last, First Middle % First Last % First Middle Last". In this case
it's a performance gain (trading off on storage space, of course).
The % is just a delimiter to prevent matches across name
permutations.<br>
<br>
Ted<br>
</body>
</html>