Question on relaxation of certain schema 'Regex Pattern Restrictions'

[MrChocolateMoose]

I read through the Schema Regex Pattern Restrictions.

I thought about the restrictions in conjunction with each other and most were probably fine, but the paint points I felt were:

No Lookaheads/Lookbehinds: (?=pattern), (?!pattern), (?<=pattern), (?<!pattern)

Some queries become almost silly hard, but still "possible", without using this (e.g. search string and make sure that it does not contain TODO or TBD [my understanding is that using negative lookaheads is the best way to do this). I think this rule might cause folks to spend more time than they like to admit trying to work within the constraints for anything more than simple regexes.

[not documented] No global options / "special groups"

Global options for using things like case insensitive mode. It's not a big deal to have to [Ss][Pp][Ee][Ll][Ll] it out, but would be a QOL thing.

Not sure how hard it is to relax at least the no lookaheads/lookbehinds assumption w/ the ecosystem you're building. My understanding is that the restriction likely comes from SQLite syntax?

If it's a non-starter due to safety qualification or library restrictions, then my only thoughts is that it might help to think through more examples of how to make certain more complex regexes that have practical value in a world with all of those constraints listed.

For the global options one, if it is a non-starter, then the special groups limitation should probably be documented.