Home » SQL & PL/SQL » SQL & PL/SQL » Behaviour of Timestamp DataType
Behaviour of Timestamp DataType [message #228256] Mon, 02 April 2007 05:02 Go to next message
saurabhsoni
Messages: 3
Registered: April 2007
Location: Indonesia
Junior Member

Hi

I am using a db which is being updated on realtime basis. In my db I am using timetamp as datatype for few of the fields.Now I had observed that whenever a record comes which has a value fro that column greater than the current time then it takes long time to insert that record in to db.There is no constraint defined on that field.So my question is : Is there any limitation on timestamp datatype that it can't accept a value greater than the current time?

Thanks in advance....

Saurabh
Re: Behaviour of Timestamp DataType [message #228365 is a reply to message #228256] Mon, 02 April 2007 12:57 Go to previous messageGo to next message
Michel Cadot
Messages: 64122
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

No.

Regards
Michel
Re: Behaviour of Timestamp DataType [message #228377 is a reply to message #228256] Mon, 02 April 2007 15:08 Go to previous messageGo to next message
Bill B
Messages: 1484
Registered: December 2004
Senior Member
It shouldn't make any difference. Do you have any constraints or triggers on the table. Is it happening on ANY insert, or only those with a timestamp in the future?
Re: Behaviour of Timestamp DataType [message #228429 is a reply to message #228377] Tue, 03 April 2007 00:31 Go to previous messageGo to next message
saurabhsoni
Messages: 3
Registered: April 2007
Location: Indonesia
Junior Member

Thanks for your rely ......

There is no constraint or trigger defined on that particular coulmn.And its not happening on ANY insert it is partcularly for those records only for which I am getting the values in future date(may be 6 or 7 hrs ahead of current time) or sometimes for next date also.

Thanks

Saurabh
Re: Behaviour of Timestamp DataType [message #228531 is a reply to message #228429] Tue, 03 April 2007 05:20 Go to previous message
orausern
Messages: 817
Registered: December 2005
Senior Member
Quote:

it is partcularly for those records only for which I am getting the values in future date(may be 6 or 7 hrs ahead of current time) or sometimes for next date also.



so with this info, you create a test case and prove or disprove. I mean , try to manually insert such a record in the db(i mean a record having similar characteristic) and check for yourself and post the findings.

Previous Topic: How to load data from an excel sheet to a global temporary table using SQLLDR
Next Topic: Need inputs for inserting data in DB from .dat file.
Goto Forum:
  


Current Time: Wed Dec 07 04:50:04 CST 2016

Total time taken to generate the page: 0.18458 seconds