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


Yes, that was something that naturally came to mind so I did try it and 
it does solve the problem of the zero valued date.  However, my 
objective is to develop a database file (i.e., .odb) that I can send to 
a community of users who may lack the technical savvy to wrestle with 
prerequisite setup requirements.  In this sense ODBC is a bit of a 
beast.  It seems to rely on something that Windows refers to as data 
sources which are external to the .odb file.  There are lots of options 
which would make one think that it should be possible to invest in some 
extra work when creating the .odb file that makes life simpler for the 
technically challenged community of users. However, I wasn't able to 
achieve such a result.  In fact it appears as though LibreOffice Base 
does not even allow the use of what Windows calls the file type of data 
source.

Both ODBC and JDBC require my users to have connectors installed.  I 
haven't yet determined that JDBC is good enough to solve the problem, of 
having my users know about server connections, but it does look like 
more of the database (i.e., MySQL server) connection specific setup is 
confined to the .odb file.  This is why I'd like to make JDBC work.  
Insofar as zero valued dates seem to be quite natural for a MySQL 
database one would think that the MySQL supplied Connector J could deal 
with such more elegantly.

David ...

-------- Original Message --------
Subject:        Re: [libreoffice-users] Value '0000-00-00' can not be 
represented as java.sql.Date
Date:   Sat, 15 Dec 2012 17:54:39 -0500
From:   Jay Lozier <jslozier@gmail.com>
To:     users@global.libreoffice.org



On 12/15/2012 04:03 PM, receiver wrote:
I'm trying to create a LibreOffice (3.6.4) Base document which utilizes
a MySQL database.  I have installed the MySQL Connector J (5.1.22) and
have good results with one significant exception.  The subject error
prevents display of a table which does contain dates. I suspect that
this may be a problem with the JDBC connector and have reported it here
<http://forums.mysql.com/read.php?39,576155,576155#msg-576155>, however
it also seems possible that this is caused by LibreOffice Base.

Any advice on what I may have overlooked would be appreciated.

David ...

David,

What OS are you using? You might find an alternate connector at
http://dev.mysql.com/downloads/connector/ that will work. I would try
the ODBC connector for your OS.

Jay

-- 
Jay Lozier
jslozier@gmail.com


-- 
For unsubscribe instructions e-mail to: users+help@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







--
View this message in context: 
http://nabble.documentfoundation.org/Fwd-Re-libreoffice-users-Value-0000-00-00-can-not-be-represented-as-java-sql-Date-tp4024588.html
Sent from the Users mailing list archive at Nabble.com.
-- 
For unsubscribe instructions e-mail to: users+help@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

Context


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.