> Also, you neglected to add PLACING to the gram.y keyword category lists.
I just now added and committed it as a reserved word.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresq
Thanks for the info! I have a question...
> As usual: ( ) + * [ ] |
> Instead of dot . there is underscore _
> There is % to mean .* just like LIKE
> There is no ? or ^ or $
> Regular expressions match the whole string, as if there were an
> implicit ^ before and $ after the pattern. You ha
Thomas Lockhart wrote:
> Right. I'm not certain about the regex syntax defined by SQL99; I used
> the syntax that we already have enabled and it looks like we have a
> couple of other variants available if we need them. If someone wants to
> research the *actual* syntax specified by SQL99 that wou
> > How is SIMILAR TO different from ~ ?
> >From the part of Thomas's email you snipped:
>Implement SQL99 SIMILAR TO as a synonym for our existing operator "~".
> So the answer is "not at all"
Right. I'm not certain about the regex syntax defined by SQL99; I used
the syntax that we already ha
> TODO item marked as done:
> * -Add SIMILAR TO to allow character classes, 'pg_[a-c]%'
Darn. Will have to be more careful next time ;)
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Thomas Lockhart wrote:
> I've just committed changes which implement three SQL99 functions and
> operators. OVERLAY() allows substituting a string into another string,
> SIMILAR TO is an operator for pattern matching, and a new variant of
TODO item marked as done:
* -Add SIMILAR TO to al
On Tue, Jun 11, 2002 at 11:08:11AM -0700, Josh Berkus wrote:
> Thomas,
>
> > I've just committed changes which implement three SQL99 functions and
> > operators. OVERLAY() allows substituting a string into another string,
> > SIMILAR TO is an operator for pattern matching, and a new variant of
>
Thomas,
> I've just committed changes which implement three SQL99 functions and
> operators. OVERLAY() allows substituting a string into another string,
> SIMILAR TO is an operator for pattern matching, and a new variant of
> SUBSTRING() accepts a pattern to match.
Way cool! Thank you ... this
> Also, you neglected to add PLACING to the gram.y keyword category lists.
OK. I'm also tracking down what seems to be funny business in the regex
pattern caching logic, so will have a couple of things to fix sometime
soon.
- Thomas
---(end of broadcast)
I've just committed changes which implement three SQL99 functions and
operators. OVERLAY() allows substituting a string into another string,
SIMILAR TO is an operator for pattern matching, and a new variant of
SUBSTRING() accepts a pattern to match.
Regression tests have been augmented and pass.
Also, you neglected to add PLACING to the gram.y keyword category lists.
(Perhaps someone should whip up a cross-checking script to verify that
everything known to keywords.c is listed exactly once in those gram.y
lists.)
regards, tom lane
---(end
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> I've just committed changes which implement three SQL99 functions and
> operators.
I'm getting
gcc -O1 -Wall -Wmissing-prototypes -Wmissing-declarations -g -I../../../../src/include
-c -o regexp.o regexp.c
regexp.c: In function `textregexsubstr':
I've just committed changes which implement three SQL99 functions and
operators. OVERLAY() allows substituting a string into another string,
SIMILAR TO is an operator for pattern matching, and a new variant of
SUBSTRING() accepts a pattern to match.
Regression tests have been augmented and pass.
13 matches
Mail list logo
