On Mon, May 9, 2016 at 2:20 PM, Richard Hipp <drh at sqlite.org> wrote: > On 5/9/16, Chris Brody <chris.brody at gmail.com> wrote: >> On Wed, May 4, 2016 at 2:52 PM, Richard Hipp <drh at sqlite.org> wrote: >>> On 5/4/16, Bhagwat Balshetwar <bhagwat.balshetwar at gmail.com> wrote: >>>> I want to write the custom function for regular expression using C/C++. >>> >>> You mean like this one: >>> https://www.sqlite.org/src/artifact/a68d25c659bd2d89 >> >> Is there any reason this cannot be included as an option in the SQLite >> amalgamation? >> > > The code above does not implement PCRE. And so some people would have > issues with it. And then we'd end up having add PCRE support too, > while continuing to support both the fast regular expression in the > extension above for backwards compatibility. This is a nightmare that > I don't want to get mixed up with if I don't have to.
Understood, thanks for the answer. In general I wish there were an easier way to switch REGEXP implementations. I do notice that SQLite does support pluggable components and extensions, through I wonder if this could be made easier somehow.
