It looks like this is going to fail as you added the method to the query classes yet you're calling it from the driver class.

Also, we need a method in the base driver/query class (whichever it is supposed to be in) otherwise it'll need to be wrapped in a method_exists() check as I don't see a method here for SQL Server.

@mbabker you are right my fault, hope better now

for the SQL server based on this http://www.sql-workbench.net/dbms_comparison.html we are in trouble

so i ask why we need a posix pattern matching in module/template/style search ?
for db's portability should be better the trivial LIKE

Can't say I have an answer for that one, but if it works the same with a LIKE then go for it.

i've switched the 3 models from REGEXP to LIKE

despite i don't have a clue for MSSQL posix pattern matching i've added the "portability" method regexp for Mysql and Postgresql for future use

It's for future purpose
The Regexp is an operator and usually it's used mainly in where condition or this is the way I think at
So I've putted that method in the query class

@gunjanpatel
as usual my typos in the comment i've writed

* Usage:
* $query->where('field ' . $db->regexp($search));

instead of

$query->where('field ' . $query->regexp($search));

Super @alikon Thanks.

Successfully tested in postgre.

@test works with postgresql, mssql, mysql! Thanks @alikon!

It also fixes search in template manager for postgresql and mssql.

Moving to RTC! Thanks for coding and testing!

Great work @alikon!