Issue 106234 - [cws hsqldb19] Time macros are not recognized
Summary: [cws hsqldb19] Time macros are not recognized
Status: CLOSED DUPLICATE of issue 106191
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: DEV300m61
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-23 22:45 UTC by drewjensen.inbox
Modified: 2009-10-27 08:29 UTC (History)
1 user (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 drewjensen.inbox 2009-10-23 22:45:24 UTC 
Test env. OOO300m_61 CWSHSQLdb19 (10-20-09), Win 7

To reproduce.

Open Base
Go to queries
Create New query in SQL view
Click on the SQL tool button

1) test one date passes
Enter command:
CALL CURRENT_DATE
Run query - result is the current date

2) test time macro
Enter command:
CALL CURRENT_TIME
Run query - 

---------------------------
Debug Output
---------------------------
Error: ORowSetValue::fill: unsupported type!
From File d:/src/cws/hsqldb19/ooo/connectivity/source/commontools/FValue.cxx at
Line 1910

Same is true for CURRENT_TIMESTAMP

NOTE - selecting IGNORE from that error dialog sometimes the returns an empty
result set, and sometimes OO.o just crashes...can't tell you how to make it do
one or the other - but it appears that running a successful query first raises
the chances that the application will actually crash
Comment 1 drewjensen.inbox 2009-10-23 23:39:53 UTC 
Quick followup

CALL LOCALTIME
CALL LOCALTIMESTAMP

both work as expected.
Comment 2 ocke.janssen 2009-10-27 08:29:12 UTC 
It's a duplicate one.

*** This issue has been marked as a duplicate of 106191 ***
Comment 3 ocke.janssen 2009-10-27 08:29:47 UTC 
Closing it.