1.73 Filter doesn’t work (apparently in a very particular instance).

On 12/02/2013 16:20, kromkowski wrote:
> I have table called "TIME", using filter if I try to select a field,
> all that get put into the Filter box is "TIME" not "TIME.myselectedfield"
>
> I presume this is tripping up on the fact that TIME is a reserved word.
>
> In fact, if I reorg to TIMES, there is no problem.
>
> By the way, couldn't the filter box have been made editable. so that I
> can just type in the filter or fix a mistake manually instead of having
> to start completely over from beginning if I make mistake or change mind?
>

Yes, if you have tables that are the same as reserved words in SQL you will hit this problem. As for the filter box, before we can
make it editable we need to add a full parser for the SQL syntax that can handle things being built bit-by-bit. We haven't had
time to do that, which is why the box is currently not editable. Annoying we know (for us too), but it is simply much much harder
to write this sort of thing than it is to just write correct SQL.

Ciao, Neil

On 18/02/2013 19:28, kromkowski wrote:
> On 02/18/13 1:43 PM, Neil Robinson wrote:
>> On 12/02/2013 16:20, kromkowski wrote:
>>> I have table called "TIME", using filter if I try to select a field,
>>> all that get put into the Filter box is "TIME" not "TIME.myselectedfield"
>>>
>>> I presume this is tripping up on the fact that TIME is a reserved word.
>>>
>>> In fact, if I reorg to TIMES, there is no problem.
>>>
>>> By the way, couldn't the filter box have been made editable. so that I
>>> can just type in the filter or fix a mistake manually instead of having
>>> to start completely over from beginning if I make mistake or change mind?
>>>
>>
>> Yes, if you have tables that are the same as reserved words in SQL you will hit this problem. As for the filter box, before we can
>> make it editable we need to add a full parser for the SQL syntax that can handle things being built bit-by-bit. We haven't had
>> time to do that, which is why the box is currently not editable. Annoying we know (for us too), but it is simply much much harder
>> to write this sort of thing than it is to just write correct SQL.
>>
>> Ciao, Neil
>>
>
>
> I'd rather have an editable box, and let the parser fail because of my
> errors which I'd figure out and fix than having to deal with the current
> situation.
>

We've considered that mode, and will see if we can activate it for the next release. If we add it, it will use a toggle to allow
editing, but will then disable the buttons and boxes above (other than maybe the table combo and field list box).

Ciao, Neil