MySQL Forums
Forum List  »  Newbie

Storing Java Timestamp (long) in database as BIGINT?
Posted by: Ivan Yung
Date: November 24, 2010 11:19AM

Here's a table-design question....

A Java developer wants to store the Java timestamp value, which is a LONG datatype which its value represents milliseconds, directly into the table. I'm in the camp that "if you want a datetime in there, stick it to the DB as a datetime/timestamp. I just don't like having saved as BIGINT.

What's your take, and the pros/cons? The table is populated and read by the java application most of the time, and of course there will be occassional SELECT from the table for research purposes.


Options: ReplyQuote

Written By
Storing Java Timestamp (long) in database as BIGINT?
November 24, 2010 11:19AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.