search

melesch / log4jdbc

Automatically exported from code.google.com/p/log4jdbc
0 stars 0 forks source link

JDBC vs Dialect Datetime #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
JDBC uses ISO-style escape for date (e.g. MM/dd/YYYY) whereas MySQL uses ( 
YYYY-mm-DD) ... This means that while the resulting log file will have dialect 
specific SQL for many operations, the date formats will be wrong.

I would suggest 2 feature enhancement to address this issue

1) Allowing the user to specify a SimpleDateFormat string such that the SQL 
could be logged.

2) Allowing the user to specify client-side and server-side time zone 
parameters.

Original issue reported on code.google.com by jonathan...@gmail.com on 9 Jul 2010 at 4:26

GoogleCodeExporter commented 8 years ago 
The goal is to produce SQL that you can ideally cut and paste right into a SQL 
Query editor and execute against your DB.  There are RdbmdSpecifics 
implementations for Oracle and SQL Server that have their own date formatting 
for those DB implementations that work pretty well, but nobody has ever written 
one for MySql.  This wouldn't address the time zone issue, but maybe the other 
issue?  What do you think?

Original comment by arthur.b...@gmail.com on 9 Jul 2010 at 4:30

GoogleCodeExporter commented 8 years ago 
See Issue 34.  We have a candidate rdms specifics class for MySql now, although 
I haven't had time to test it.  would appreciate some feedback and testing from 
some of the mysql users out there.

Original comment by arthur.b...@gmail.com on 15 Jun 2011 at 2:05