| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Boolean operators without commutators vs. ALL/ANY |
| Date: | 2011-06-20 17:22:24 |
| Message-ID: | 1308590278-sup-512@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Florian Pflug's message of lun jun 20 06:55:42 -0400 2011:
> The latter (i.e. regexp literals enclosed by /../) probably isn't
> desirably for postgres, but the former definitely is (i.e. distinguishing
> regexp's and text in the type system). Please see the thread
> "Adding a distinct pattern type to resolve the ~ commutator stalemate"
> for the details of the proposal.
'your text' ~ regexp 'your.*foo'
column ~ regexp 'your.*foo'
So you could do
regexp 'foo.*bar' ~ 'your text'
and it's immediately clear what's up.
The question is what to do wrt implicit casting of text to regexp.
If we don't, there's a backwards compatibility hit.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-06-20 17:24:38 | Re: possible connection leak in dblink? |
| Previous Message | Tom Lane | 2011-06-20 17:22:06 | Re: proposal: a validator for configuration files |