[
https://issues.apache.org/jira/browse/EMPIREDB-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881246#comment-16881246
]
Rainer Döbele commented on EMPIREDB-291:
----------------------------------------
I selected this on Purpose, as TIMESTAMP should always be mapped to the
corresponding database's native data type and it whould have at least a
millisecond resolution. (this is unclear for DATETIME).
You may have mulitple TIMESTAMP columns per table, but Empire-db will Always
use only one as the record timestamp. By default this is the first one added,
but one can manually select another one or even set none (by calling
setUpdateTimestamp()).
The idea is, to treat DATETIME and TIMESTAMP as synonyms by default, but allow
the database or the application to distinguish between the two.
I think this adds new possibilities without affecting existing code and it is
intuitive as TIMESTAMP lives up to its name.
> Simplify table definition for update timestamp
> ----------------------------------------------
>
> Key: EMPIREDB-291
> URL: https://issues.apache.org/jira/browse/EMPIREDB-291
> Project: Empire-DB
> Issue Type: Improvement
> Reporter: Rainer Döbele
> Assignee: Rainer Döbele
> Priority: Major
>
> Simplify defining the Update-Timestamp column of a table by intoducing a
> TIMESTAMP data type like with data type AUTO_INC and INTEGER.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
