On Wed, 18 Sep 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > I'm in agreement with Thomas here ... unless a problem has been defined a
> > bit more specifically then 'it isn't posix compliant', it shouldn't be
> > considered an open item ... please remove?
> A quick review of SQL99 says that their notion of SIMILAR TO patterns
> is an unholy witches' brew: it does *both* common-or-garden regexp
> expressions and LIKE patterns. Specifically, I see these
> | OR (regexp-ish)
> * repeat 0 or more times (regexp-ish)
> + repeat 1 or more times (regexp-ish)
> % match any character sequence (like LIKE)
> _ match any one character (like LIKE)
> [...] almost-but-not-quite-regexp-ish character class
> (...) grouping (regexp-ish)
> plus a just-like-LIKE treatment of a selectable escape character.
> But the most important variation from common regex practice is that
> (if I'm reading the spec correctly) the pattern must match to the
> entire target string --- ie, it's effectively both left- and right-
> anchored. This is like LIKE patterns but utterly unlike common regexp
> I could live with the fact that our regexp patterns don't implement all
> of the spec-mandated metacharacters. But I do not think we can ignore
> the difference in anchoring behavior. This is not a subset of the spec
> behavior, it is just plain wrong.
> I vote with Peter: we fix this or we disable it before 7.3 release.
> It is not anywhere near spec compliant, and we will be doing no one
> a favor by releasing it in the current state.
What would it take to get it to a fixed state? Who implemented SIMILAR TO
in the first place? Who is able to fix this? And, finally, what are the
implications of leaving things as they are?
>From my read of what you are saying above, its currently implemented with
an implied ^ and $ around the pattern match?
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly