Filter SQL inconsistent with Local SQL

[stevemagruder]

Question: Why is the SQL allowed in TOracleDataSet.Filter not consistent with Borland's Local SQL?

Two differences (off the top of my head) are:

1) not allowing the "like" predicate but instead allowing "field = value*"--this is nice but it would also be nice to be able to use standard SQL;

2) requiring parentheses around clauses when there are two or more, even if not needed to parse out the logic (e.g., "where field1 = value1 and field2 = value2")--standard SQL doesn't have this requirement.

I'm certainly able to work around these two examples, but it's nevertheless frustrating to *have* to work around them.

Thanks,
Steve

 

[Marco Kalter]

Filter conditions are not SQL. If you prefer SQL conditions, you can of course use the SQL property instead.

------------------
Marco Kalter
Allround Automations

 

[stevemagruder]

Originally posted by mkalter:
Filter conditions are not SQL. If you prefer SQL conditions, you can of course use the SQL property instead.

Well, of course they are. A limited SQL, but SQL nonetheless. Now, how about an answer to my question?

Steve

 

[Marco Kalter]

If you check the Borland documentation, you will see that the Filter is simply not SQL. It does not specify a like operation, and uses the asterisk as wildcard character. It uses the following example:

State = 'M*'

------------------
Marco Kalter
Allround Automations