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 : http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html Alex -- For unsubscribe instructions e-mail to: users+h...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
