Issue 108593 - Base puts double quotes around (Oracle's) keyword SYSDATE in query throws "invalid identifier" error.
Summary: Base puts double quotes around (Oracle's) keyword SYSDATE in query throws "in...
Status: CONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO310m19
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-23 01:03 UTC by smithtv
Modified: 2013-08-07 15:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description smithtv 2010-01-23 01:03:08 UTC 
When running a query against an Oracle 9i database the product adds double 
quotes around key word SYSDATE causing Oracle to throw an ‘ORA-
00904: “SYSDATE”:invalid identifier’ error.

Example: SELECT * FROM "A_TABLE" WHERE "THE_DATE" > SYSDATE is changed to: 
SELECT * FROM "A_TABLE" WHERE "THE_DATE" > "SYSDATE"

:(
Comment 1 Frank Schönheit 2010-02-01 20:34:25 UTC 
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.