| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | teodor(at)sigaev(dot)ru, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: knngist - 0.8 |
| Date: | 2010-08-02 16:14:19 |
| Message-ID: | AANLkTinrnxCJDOYiUkBd-yU0J-42_5TquQXCAr+KB4Hp@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2010/7/29 Alexander Korotkov <aekorotkov(at)gmail(dot)com>:
> But, in pg_trgm it makes it possible to combine different similarity levels
> in one query. For example:
> select * from test_trgm order by t <-> 'asdf' < 0.5 or t <-> 'qwer' < 0.4;
> Is there any chance to handle this syntax also?
Maybe I'm missing something, but I don't think that ORDER BY clause
makes much sense. OR is going to reduce a true or false value - and
it's usually not that interesting to order by a column that can only
take one of two values.
Am I confused?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-02 16:27:46 | Re: (9.1) btree_gist support for searching on "not equals" |
| Previous Message | Robert Haas | 2010-08-02 16:08:14 | Re: patch for check constraints using multiple inheritance |