search

brittneybrinsfield / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Adding a new filter does not work (with REGEXP) #1770

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a new content search filter with active db in Content -view:
Search function -dropdown "Edit filters"-> new filter with Clause: 
 REGEXP '${}'
2. Use filter -> DB throws an error: 
"The table data couldn't be loaded presumably due to used filter clause. 

MySQL said: You have an error in your SQL syntax; check the manual that 
corresponds to your MariaDB server version for the right syntax to use near 
'REGEXP 'product_id' LIMIT 0,1000' at line 1"

3. REGEXP -filtering works directly in Query-view.

What is the expected output?
What do you see instead?

What version of Sequel Pro are you using? 10.0.2/build 4096
What version of OS X are you using? OS X 10.8.4
What version of MySQL are you connecting to on the server? 5.5.29-MariaDB

Please provide any additional information below.

Original issue reported on code.google.com by rop...@gmail.com on 1 Aug 2013 at 7:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Works for me.

Please provide the output of the SQL Console.
Also did you notice SP provides Regex filters by default (if the column is a 
text column)?

Original comment by schlabbe...@gmail.com on 1 Aug 2013 at 7:10

GoogleCodeExporter commented 9 years ago 
HI Ropsu,
I faced a similar issue, but I think the problem is that when you add a filter 
on SequelPro it automatically embedds a structure of  "SELECT * FROM <TABLE> 
where <FIELD>" as can be seen in one of the screenshots you attached.. With 
regex maybe this initial query is not so beneficial.  Have you found a solution 
for it?

Original comment by tabata.h...@trademob.com on 6 Sep 2013 at 2:29