• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2203
  • Last Modified:

Oracle DATE to TIMESTAMP conversion

I am using oracle 9i currently we use date datatype in couple of fields.
what are the possible risks if we use TIMESTAMP datatype instead of DATE?


0
bondzoro
Asked:
bondzoro
2 Solutions
 
sujith80Commented:
- Timestamp takes more space. Around 13 bytes, Compared to date - 7 bytes.
- If your application doesnt requires precision upto timestamp go for date
0
 
Stephen LappinSenior TechnologistCommented:
Discoverer does not support TIMESTAMP.
There can be issues with timezone and daylight savings when comparing TIMESTAMPS.

If all you need it the time to the nearst second, I would recommend that yuu stick with DATE.
0
 
schwertnerCommented:
USE TIMESTAMP only if you need fraction of seconds.
There is no risk to use it. By default it stores dates with 6 digits after the decimal
points of the seconds.
TIMESTAMP with TIMEZONE is more complex and causes more errors
by different applications.
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now