SIMILAR TO syntax (Was: Re: The TODO List (Was: Re: O...) - Mailing list pgsql-hackers

From Marc G. Fournier
Subject SIMILAR TO syntax (Was: Re: The TODO List (Was: Re: O...)
Date
Msg-id 20020919132206.S53125-100000@hub.org
Whole thread Raw
In response to Re: The TODO List (Was: Re: Open 7.3 items)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SIMILAR TO syntax (Was: Re: The TODO List (Was: Re: O...)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 19 Sep 2002, Tom Lane wrote:

> "Marc G. Fournier" <scrappy@hub.org> writes:
> > Who implemented SIMILAR TO in the first place?
>
> Thomas.  He put in the syntax, but as it stands it's simply syntactic
> sugar for ~ --- that is, our Posix-compatible regex match operator.
> Since the spec demands very non-Posix behavior, this is wrong.
>
> AFAICS, getting SIMILAR TO to operate per spec would require adding some
> sort of translation function that converts the spec-style pattern into
> a Posix pattern that our regex match engine would handle.  This would at
> least require adding ^ and $ around the pattern, converting the escape
> character if any, and translating % and _ into .* and . respectively.
> There are probably some differences of detail that we'd need to fix
> later, but that would get it to a state where we need not be ashamed
> to release it.
>
> We already have a similar mechanism for handling LIKE ... ESCAPE
> clauses, so it doesn't seem too difficult to do.  But I haven't got
> time for it...

'K, just curious here, but ... Thomas, do you agree with Tom's
interpretation of the spec?  If so, would it be possible to get the above
fixed?

Or is there an ambiguity there (not like *that* has never happened before)
that Tom/Peter are being more strict about then the spec requires?





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal for resolving casting issues
Next
From: "Marc G. Fournier"
Date:
Subject: Re: [GENERAL] PGXLOG variable worthwhile?