MySQL-JDBC-Connector

users
#1

Hello,
I am using the JDBC-MySQL-Connector under LO 4.2.5 (and 4.3.0-RC2) and have
a rather "weird" experience:
There is a table within my database by the name of "inventar" (German for
"inventory"). It is defined like this
CREATE TABLE inventar
   (nummer INTEGER NOT NULL,
    bezeichnung VARCHAR (255) not null default 'Hängemappe',/* ä = a-Umlaut */
    stueckZahl INTEGER not null default 1,
    anschDatum DATE not null DEFAULT '1999-09-01',/* Anschaffungsdatum */
    fvbNr INTEGER not null default 0, /* Firmennummer des Lieferanten */
    typBesch CHAR(1) not null default 'k', /* Miete, Kauf, Leihe, Spende,... */
    anschKosten FIXED (11,2) default 0, /* Anschaffungskosten in EUR */
    repKosten FIXED (11,2) default 0, /* aufgelaufene Reparaturkosten in EUR */
    abschreibung FIXED (11,2) default 0, /* aufgelaufene Abschreibung in EUR */
    datEliminiert DATE NOT NULL DEFAULT '2099-09-01',/* aus Inventar ausgeschieden am... */
    vorhanden SMALLINT NOT NULL default 1, /* Menge laut Inventur */
    invDat DATE not null default '1999-09-01',/* Inventur-Datum */
    bemerkung VARCHAR (255) not null default ' ',
    PRIMARY KEY (nummer),
    INDEX (fvbNr),
    INDEX (typBesch),
    FOREIGN KEY (fvbNr) REFERENCES fvbPartner(nummer),
    FOREIGN KEY (typBesch) REFERENCES invBeschTyp(code)
   )
   CHARACTER SET latin1 COLLATE latin1_german1_ci
   ENGINE=InnoDB

Output of describe command using MySQL-Client 5.5):

#2

Hi Heinrich,

Have you tried setting your codepage collation to UTF-8 in at least the
driver parameters (you might have to force it too in the table). This
vaguely rings a bell with a problem I once had.

Alex