The gwt-Listbox where the comparison is defined, e.g. "is", "is not", "like", etc. Needs to have two options added for "in list" and "not in list". If either of these are selected, I need for the gwt-Suggestbox to change to a button that initiates a Javascript callback. The callback needs to be configurable so that I can add some Javascript (and server code) that prompts the user to upload a file that has a list of values. I will use the list to create a temp table and do something like:
SELECT x,y,z FROM foo f WHERE EXISTS (SELECT 1 FROM temp_table t WHERE f.x = t.x)
or
SELECT x,y,z FROM foo f
INNER JOIN temp_table t
ON t.x = f.x
This should be added as a new type in meta.types, that would probably be ideal. If you have some input as to a better way to compare a big list against a query and use EXISTS/NOT EXISTS against that list, I'm open to suggestions. Our problem is that the list could be quite large which precludes us from using IN/NOT IN.
The gwt-Listbox where the comparison is defined, e.g. "is", "is not", "like", etc. Needs to have two options added for "in list" and "not in list". If either of these are selected, I need for the gwt-Suggestbox to change to a button that initiates a Javascript callback. The callback needs to be configurable so that I can add some Javascript (and server code) that prompts the user to upload a file that has a list of values. I will use the list to create a temp table and do something like:
SELECT x,y,z FROM foo f WHERE EXISTS (SELECT 1 FROM temp_table t WHERE f.x = t.x)
or
SELECT x,y,z FROM foo f INNER JOIN temp_table t ON t.x = f.x
This should be added as a new type in meta.types, that would probably be ideal. If you have some input as to a better way to compare a big list against a query and use EXISTS/NOT EXISTS against that list, I'm open to suggestions. Our problem is that the list could be quite large which precludes us from using IN/NOT IN.