DbForge doesn't handle DEFINE correctly
Posted: Wed 17 Mar 2021 15:05
Hi,
I've raised a ticket for this but just wanted to check if anyone had found the same problem or a workaround.
I'm using DEFINE in a query block and the following works fine in SQLPlus, SQLDeveloper, TOAD but not in DbForge
DEFINE nowzz = 'TO_TIMESTAMP_TZ(''2021-3-17 12:33:8 +00:00'', ''YYYY-MM-DD HH24:MI:SS TZH:TZM'')';
SELECT &nowzz AS NowTime FROM dual;
If I run the above in DbForge I get
NOWTIME
-------
)
If I run the same in SQLPlus or SQL Developer I get
old:SELECT &nowzz AS NowTime FROM dual
new:SELECT TO_TIMESTAMP_TZ('2021-3-17 12:33:8 +00:00', 'YYYY-MM-DD HH24:MI:SS TZH:TZM') AS NowTime FROM dual
NOWTIME
--------------------------------
17-MAR-21 12.33.08.000000000 GMT
Anyone else found a similar issue?
I've raised a ticket for this but just wanted to check if anyone had found the same problem or a workaround.
I'm using DEFINE in a query block and the following works fine in SQLPlus, SQLDeveloper, TOAD but not in DbForge
DEFINE nowzz = 'TO_TIMESTAMP_TZ(''2021-3-17 12:33:8 +00:00'', ''YYYY-MM-DD HH24:MI:SS TZH:TZM'')';
SELECT &nowzz AS NowTime FROM dual;
If I run the above in DbForge I get
NOWTIME
-------
)
If I run the same in SQLPlus or SQL Developer I get
old:SELECT &nowzz AS NowTime FROM dual
new:SELECT TO_TIMESTAMP_TZ('2021-3-17 12:33:8 +00:00', 'YYYY-MM-DD HH24:MI:SS TZH:TZM') AS NowTime FROM dual
NOWTIME
--------------------------------
17-MAR-21 12.33.08.000000000 GMT
Anyone else found a similar issue?