Submitted by Armando on 2013/07/02 16:01
[EDIT 2013 07 02]
Actually, it just partially works.
More later.
[/EDIT]
 
[EDIT 2013 07 03]
It seemed to work because half of the filter (in the example below) still worked : "IDItem in (167233)" worked, but not "check is null"
[/EDIT]
 
=========
Not sure why I never tried it, but it seems to work.
 
 
 
  • Double hyphen ( -- ) complies with the ANSI/ISO standard for SQL.
  • Braces ( { } ) are an Informix extension to the ANSI/ISO standard.
  • C-style slash-and-asterisk ( /* . . . */ ) comply with the SQL-99 standard.
 
 
I tried "--" and it works well.
 
E.g. : IDItem in (167233) | check is null -- THIS IS A TEST FILTER
 
Commenting filters can of course be useful when you're not sure what ID items are there, or with long/complex queries

Comments

Would this be easy to add, Pierre ?
Since there are no "named filters", commenting filters-- as it's been suggested in the past -- would help A LOT.
 
But since you're in debugging + calendar, If this means a lot of thinking etc., forget it.
 
-------------------------------------------------------
Windows 8
Sony Vaio S Series 13 (SVS131E21L)
Ram:8gb, CPU: Intel i5-3230M, 2.6ghz

Starting v0.9.26PreRel11, comments are now allowed on the filter. Use the "--" syntax:
 
i.e. DueDate < Now -- Will only show overdue items
 
HTH !
 

Armando

2013/07/04 11:53

Permalink

Very cool ! Will download right away.
 
 
-------------------------------------------------------
Windows 8
Sony Vaio S Series 13 (SVS131E21L)
Ram:8gb, CPU: Intel i5-3230M, 2.6ghz