Currently, bugzilla lets you use a perl regexp to set the default groups for new users. In discussion, its come up that this is overkill. Instead, we should provide for a | separated list of 'things to match on the RHS of the address'. This would allow us to do queries in the db (which doesn't support perl regexps, although we can use POSIX ones instead. It would also be easier for admins to set up correctly.

keep in mind that sometimes you might want to set a group regexp that matches stuff on the LHS, too. ^(paul|george|harry)\@mydomain.com$

I'd rather not see the regexps go all the way back to GLOB-type patterns. How about using the POSIX regexps and providing some help for admins who don't understand. We could let the system use POSIX regexps internally, but let a param cause the administrative UIs to simplify the interface.

neither Sybase nor Postgres support regexps. (Postgres does with a third-party add-on in contrib, but no idea how up-to-date that is)

Postgres seems to support POSIX regular expressions.... http://www.postgresql.org/docs/view.php?version=7.3&file=functions-matching.html#FUNCTIONS-POSIX-REGEXP It also mentions an "SQL99" Regexp that looks like a compromise between a POSIX re and the "like" operation. Does Sybase support anything??? ;-)

what joel said. The operator is different, but we be be able to install a custom operator to use the same syntax from within the .cgi.

Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.

Regexps see to have worked fine for the past decade. Gerv