timestamp - behaviour does not match documentation

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
albourgz
Posts: 160
Joined: Wed 06 May 2009 12:17
Location: belgium

timestamp - behaviour does not match documentation

Post by albourgz » Tue 30 Aug 2016 12:58

Hi,

According to documentation of unidac, timestamp can be specified as this:
{timestamp '2006-12-31 23:59:59'}

However, if I run in a TUniQuery:
INSERT INTO JOBLIST(ID, DTIN, DTOUT, CUSTOMER, QTY, SUBJECT, REF, SENDNOTE, DTTRT,PROCBY, DONE, CLIENT, REROUBY, DTASKED, DTPROMISED, ARCHIVE, DTREC, NICKNAME, REFCDE, FACTSTATE, NUMORDER, OWNER, SENDBACKFILE, RETURNFILENAME,
RETURNFILENAME2, CARDQTY, FeedbackConfirmationFile, BAT, INTERNALJOB, ORDERTYPE, EXTERNALORDERID, ACCOUNTINGINVOICE) VALUES (127950, {timestamp '2016-08-30 14:44:59'}, {timestamp '1900-01-01 00:00:00'},
4443, 0, '46501plp.Xml', '2016083014445801', '', {timestamp '2016-08-30 14:44:59'}, 25,'N', 'Isabel Nv/sa', 0, {timestamp '1900-01-01 00:00:00'}, {timestamp '1900-01-01 00:00:00'}, '46501PLP.XML.ZIP',
{timestamp '1900-01-01 00:00:00'}, 'ISAP', '', 0, 0, 1, 'N', '', '', 0, '', 'N', 'N', '', NULL, '')

I get an error: hour must be between 1 and 12.
I can see in dbmonitor that hh24 is not used to format the hour.

How can I specify 15.30 (for 3.30 pm)?

I saw in a very old thread that there was a Option TimedFormat that doesn't exist anymore for oracle.
Kind regards,

MaximG
Devart Team
Posts: 1822
Joined: Mon 06 Jul 2015 11:34

Re: timestamp - behaviour does not match documentation

Post by MaximG » Mon 12 Sep 2016 12:37

Please check the needed behavior using the current UniDAC version 6.4.14 (08-Sep-16)

Post Reply