To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=108593


User fs changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|dbaneedsconfirm           |oj
--------------------------------------------------------------------------------
          Ever confirmed|                          |1
--------------------------------------------------------------------------------
                  Status|UNCONFIRMED               |NEW
--------------------------------------------------------------------------------
                 Summary|Base puts double quotes ar|Base puts double quotes ar
                        |ound keyword SYSDATE in qu|ound (Oracle's) keyword SY
                        |erry throws "invalid ident|SDATE in query throws "inv
                        |ifier" error.             |alid identifier" error.
--------------------------------------------------------------------------------
        Target milestone|---                       |OOo 3.x
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Mon Feb  1 20:34:25 +0000 
2010 -------
fs->oj: Would be great if we could enhance our parser to accept a
runtime-defined list of additional tokens. That is, instead of hard-coding the
SYSDATE identifier in the parser, we should have a per-datasource(-type) list of
additional identifiers, which are accepted by the parser.

---------------------------------------------------------------------
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]

Reply via email to