To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=91192
------- Additional comments from [EMAIL PROTECTED] Tue Jul 1 13:52:27 +0000
2008 -------
fs->oj: please review the attached patch.
The problem here seemed to me (at least to me) that in
OSQLParseNode::negateSearchCondition, the "like_predicate" rule was handled as
if it were defined as follows
like_predicate:
row_value_constructor sql_not SQL_TOKEN_LIKE ...
while in fact it is defined as
like_predicate:
row_value_constructor SQL_TOKEN_NOT SQL_TOKEN_LIKE ...
| row_value_constructor SQL_TOKEN_LIKE ...
Adding a special handling to the negateSearchCondition for like_predicate only
fixed the problem for me.
If you approve the patch, I will commit it to dba30f, and target it to 3.0.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
