Filter popup window doesn't properly build the query

vieten / sequel-pro

Automatically exported from code.google.com/p/sequel-pro

Other

0 stars 0 forks source link

Filter popup window doesn't properly build the query #1255

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. View content in table and hit COMMAND-F
2. Type a string in one of the fields

What is the expected output? What do you see instead?
I expect to see a WHERE statement populated with the text from the field that 
I'm writing. But instead I just see an empty "LIKE  '%%'" string.

What version of Sequel Pro are you using? What version of MySQL are you
connecting to on the server?
Sequel Pro: 0.9.9.1
MySQL: 5.5.15
OSX: 10.7.2 

Please provide any additional information below.
I've attached a screenshot

Original issue reported on code.google.com by ben.mid...@lendio.com on 6 Jan 2012 at 11:42

Attachments:

[Screen Shot 2012-01-06 at 4.37.12 PM.png](https://storage.googleapis.com/google-code-attachments/sequel-pro/issue-1255/comment-0/Screen Shot 2012-01-06 at 4.37.12 PM.png)

GoogleCodeExporter commented 9 years ago

I can't even input anything in the fields so there definitely seems to be an 
issue here.

Original comment by schlabbe...@gmail.com on 3 Mar 2012 at 8:44

Changed state: Accepted
Added labels: Component-Logic, Component-UI, Priority-Medium, Type-Defect, Usability

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Issue 1261 has been merged into this issue.

Original comment by schlabbe...@gmail.com on 3 Mar 2012 at 9:49

GoogleCodeExporter commented 9 years ago

I noticed this behaviour as well. Since it did work in previous releases, it 
must have become broken along the way.

It is however not completely broken, since entering "null" in one of the fields 
does build the correct query.

Which led me to the workaround: I enter "=1" in a field and it gets translated 
to `field` = 1

Just my 2c worth.

Original comment by mich...@ingoedebanen.nl on 17 Jul 2012 at 11:57

GoogleCodeExporter commented 9 years ago

The bug described by me above is fixed in r3746

I can't reproduce the other one bug I guess you have changed the "Default 
operator" setting in the gear menu.
This must contain an "@" as the variable.

Original comment by schlabbe...@gmail.com on 25 Jul 2012 at 6:33

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

There was also a Lion issue - this has been fixed in r3750, which also 
redesigns the filter popup windows to no longer use a few custom views limiting 
future compatibility.  Suggestions for design issues gratefully received :)

Original comment by rowanb@gmail.com on 29 Jul 2012 at 9:41