I can't tell you how grateful I am that you posted this workaround,
Barry! Just in time for a site launch.
Like you said, I wonder if the multiple calls to to_tsquery() are
acceptable or if there's a more graceful solution here for the long-
term.
On May 13, 9:01 pm, Barry Pederson <[EMAIL PRO
Dave Lowe wrote:
> It worked prior to qsrf-merge. I have tried adding the quotes though,
> without success.
>
> On May 13, 9:59 am, David Cramer <[EMAIL PROTECTED]> wrote:
>> The database engine usually can't fill that in anyways, you should
>> probably quote it yourself (correct me if I'm wrong)
It worked prior to qsrf-merge. I have tried adding the quotes though,
without success.
On May 13, 9:59 am, David Cramer <[EMAIL PROTECTED]> wrote:
> The database engine usually can't fill that in anyways, you should
> probably quote it yourself (correct me if I'm wrong).
>
> On May 13, 9:15 am, D
The database engine usually can't fill that in anyways, you should
probably quote it yourself (correct me if I'm wrong).
On May 13, 9:15 am, Dave Lowe <[EMAIL PROTECTED]> wrote:
> Ever since the querset-refactor merge, params in the 'tables' argument
> don't seem to be filled. The documentation d
Ever since the querset-refactor merge, params in the 'tables' argument
don't seem to be filled. The documentation describes the arguments
'params' and 'select_params' as being for where and select statements,
respectively. Do we need a "tables_params" argument as well?
Here's a code sample of whe
