Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

Le 17/12/2012 04:41, Brian Barker a écrit :

Hi Brian,

Wouldn't a better solution be to construct your database so that you
didn't need to represent this thrice-inappropriate date value?

The problem stems from the fact that the MySQL JDBC driver can not
handle Java null dates, which were permissible under previous versions
of the JDBC connector (version 3.x as far as I recall). For example, in
previous versions of the connector, fields defined as DATE NULL would,
if not filled by user input, be converted to the invalid date string
'0000-00-00' instead of NULL. This has changed with the transition to
version 5 of the connector with the consequence that some tables from
databases made previously have these '0000' invalid date strings in them.

In order to allow backwards compatibility with the 3.x driver version,
MySQL introduced the extra parameter :


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.