Re: Status report: regex replacement

On Wed, 5 Feb 2003, Tom Lane wrote:

> 1. There are a couple of minor incompatibilities between the "advanced"
> regex syntax implemented by this package and the syntax handled by our
> old code; in particular, backslash is now a special character within
> bracket expressions.  It seems to me that we'd better offer a switch
> to allow backwards compatibility.  This is easily done as far as the
> code is concerned: the regex library actually offers three regex
> flavors, "advanced", "extended", and "basic", where "extended" matches
> what we had before ("extended" and "basic" correspond to different
> levels of the POSIX 1003.2 standard).  We just need a way to expose
> that knob to the user.  I am thinking about inventing yet another GUC
> parameter, say
> 
>     set regex_flavor = advanced
>     set regex_flavor = extended
>     set regex_flavor = basic
[snip]
> Any suggestions about the name of the parameter?

Actually I think 'regex_flavor' sounds fine.

Jon