From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Klint Gore <kg(at)kgb(dot)une(dot)edu(dot)au> |
Cc: | "Joshua D(dot)Drake" <jd(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, Paul Lambert <paul(dot)lambert(at)autoledgers(dot)com(dot)au> |
Subject: | Re: Using MS Access front-end with PG] |
Date: | 2007-04-04 03:50:51 |
Message-ID: | 15322.1175658651@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Klint Gore <kg(at)kgb(dot)une(dot)edu(dot)au> writes:
> Is there any way to create operators to point like to ilike? There
> doesn't seem to be a like or ilike in pg_operator (not in 7.4 anyway).
Actually it's the other way 'round: if you look into gram.y you'll see
that LIKE is expanded as the operator ~~ and ILIKE as the operator ~~*
... so one of the alternatives I was thinking of offering to Paul was
to rename those two operators to swap 'em. However I'm afraid that
that would break the planner, which has some hardwired assumptions
about the behavior of those two operator OIDs. Maybe we should change
the planner to look a level deeper and see what functions the operators
refer to.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma Jr | 2007-04-04 04:02:01 | Re: Using MS Access front-end with PG |
Previous Message | Marcus Engene | 2007-04-04 03:41:28 | Re: speeding up a query |
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2007-04-04 04:28:36 | Re: Using MS Access front-end with PG] |
Previous Message | Joshua D. Drake | 2007-04-04 03:22:31 | Re: Using MS Access front-end with PG] |