on 07-19-2016 11:46 AM
The object SQL should simply be CURRENT_DATE
It will not parse but it will work fine when you use it with other objects that are based on tables.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Do you want me to use any one of the below syntaxes ?
1.SELECT
date(current_Date) from dual;
2.select add_months(current_date,0) from dual;
3.SELECT Current_Date AS ANSI_Date
or else simply current_date,
-------------------------------------------------------------
My customer used previous syntax i.e., SELECT
date(current_Date) from dual; and is working fine in db level .
When he tried date(current_Date) from dual; in universe it will not parse ,even though do I continue in report with this object?
As I said yesterday, it won't parse. Just use it with table-based objects. The parser is expecting a table (e.g. SALES_FACT.SALES_VALUE) but system functions work differently and where no input is required, such as CURRENT_DATE, you won't parse them. Don't associate a table with it to get it parsed because then you'll include that table in every query, whether you need it or not and will potentially get wrong results.
Try this sql for netezza, if you only need the current date or if you are fetching it from any table use the table name instead of dual:
Select date(Current_date) from dual
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.