Re: the best practice to deal with datetime in mysql using jdbc?
Lew wrote:
only in MySQL, AFAIK. Certainly not in any
other DBMS that claims SQL compliance.
Arne VajhQj wrote:
SQLServer 2005 BOL:
Well, shiver me timbers.
I stand corrected, sort of.
<http://msdn2.microsoft.com/en-us/library/ms182776.aspx>
The Transact-SQL timestamp data type is different from the timestamp data type
defined in the SQL-2003 standard. The SQL-2003 timestamp data type is
equivalent to the Transact-SQL datetime data type.
We see ever more strongly as you wrote:
using a database without reading basic documentation
has always been a risky business.
I actually don't mind that SQL is such a loose standard. The areas like this
are cognate enough, for all that they could be tricky if we ignore the RTFM
advice, that at least we don't necessarily have to change our Java code for
them if we make the right translations between the SQL platforms.
Most of the differences between SQL dialects fall in the area of enhancements,
such as the variants of LIMIT ... OFFSET and the various flavors of subqueries
as columns, temporary views or tables, update clauses and whatnot. More
important differences exist in the support of OLAP and scalable, stable
deployment.
As a programmer who is more used to Standard-ish-esque-like SQLs like Oracle
and Postgres, I can no more afford to be parochial in my approach to DBMSes
than can those weaned on the Microsoft / MySQL diet. It's handy to turn up
Rosetta Stones like one mentione a few times hereabouts,
<http://troels.arvin.dk/db/rdbms/>
which specifically mentions TIMESTAMP:
<http://troels.arvin.dk/db/rdbms/#data_types-date_and_time-timestamp>
and also auto-sequencing keys, another biggie:
<http://troels.arvin.dk/db/rdbms/#mix-identity>
--
Lew