Re: [libreoffice-users] JDBC params - the J "null date" problem

2015-02-02 Thread Mark Stanton 
In article <54cf6b6e.6030...@aon.at>, Heinrich Stöllinger wrote:
> Also - one obviously specify MORE than just ONE parameter in the connection
> string, such as
> dbname?autoReconnect=true&zeroDateTimeBehavior=convertToNull
> Heinrich
> Alex Thurgood schrieb:
> > The way is to add the parameter in the field where you specify which
> > database to connect to :
> >
> > nameofmydb?zeroDateTimeBehavior=convertToNull

Thanks both!
Mark Stanton
One small step for mankind...



-- 
To unsubscribe e-mail to: users+unsubscr...@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

[libreoffice-users] JDBC params - the J "null date" problem

2015-02-02 Thread Mark Stanton 
I'm accessing a MariaDb (howzatt Tom? ;-) ) database through a JDBC 
connection on Linux (the native connector doesn't work, not sure why, 
yet). When accessing a datetime column with some rows set to 
'-00-00 00:00:00' Base complains and refuses due to this being an 
invalid (js) date.

I note from a quick search that this is a well known problem. There 
are some solutions involving to the JDBC connector load string, which 
seems to not be accessible from Base. Is that a good idea?

The only solution that I've found involves casting the field to a 
string. It works, but I'd prefer not to have to.

Is there something I've missed?

Mark Stanton
One small step for mankind...



-- 
To unsubscribe e-mail to: users+unsubscr...@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