Hello,
Seeing as the Native MySQL-connector seems to be a "difficult" birth -
I tried both ODBC and JDBC lately. Unfortunately both seem to be unusable!
JDBC: I cannot get it to accept German special characters (even though I
specify codepage ISO-8859-15/EURO).
Also, when inserting you rows into the database, both with JDBC and ODBC,
string default values are shown with apostrophies at the beginning and end.
If one then re-selects the row, the fields are shown correctly
(i.e. without the apostrophies). This might be kind of o.k. for me as I
have around 30 years of IT-experience behind me, but certainly NOT o.k. for
the average uninitiated user...
ODBC: default values as specified within a table creation show kind of "random"
values in columns of inserted tuples. When refreshing the display or re-selecting
the tuplethe values are displayed correctly.
I yearn for the native connector but unfortunately really DON't have the time
to build it myself...
Regards
Heinr
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
--
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
- [libreoffice-users] BasIe - connecting through JDBC · Heinrich Stoellinger
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.