Re: mysql v3 with connector/J

Am Dienstag, den 12.07.2005, 12:52 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
> 
> > Type: com.sun.star.sdbc.SQLException
> > Message: GDS Exception. 335544665. violation of PRIMARY or UNIQUE
> > KEY constraint "INTEG_65" on table "TestTab"
> > ...
> > The server log show no entry, so the exception is inside OOo(1.1).
> 
> The above error message is most probably not generated by OOo, but by
> either the DB backend or the driver.
> 
> I suppose there's a unique index on the table in question, and the value
> you're trying to insert into the respective columns is, well, not unique.
> You can probably find the index name ("INTEG_65") in the table design in
> the Indexes dialog. See which columns are part of the index, and verify
> that the value you're trying to insert into those columns really are unique.

No, no index but the primary key defined, values 1-18 in the table,
trying to insert 20, 111 or something.

mysql tells me:

mysql> describe TestTab;
+-------+---------------+------+-----+---------+-------+---------------------------------+
| Field | Type          | Null | Key | Default | Extra | Privileges                      |
+-------+---------------+------+-----+---------+-------+---------------------------------+
| A     | int(11)       |      | PRI | 0       |       | select,insert,update,references |
| B     | varchar(50)   | YES  |     | NULL    |       | select,insert,update,references |
| C     | double        | YES  |     | NULL    |       | select,insert,update,references |
| D     | float         | YES  |     | NULL    |       | select,insert,update,references |
| E     | decimal(12,2) | YES  |     | NULL    |       | select,insert,update,references |
| F     | date          | YES  |     | NULL    |       | select,insert,update,references |
| G     | date          | YES  |     | NULL    |       | select,insert,update,references |
+-------+---------------+------+-----+---------+-------+---------------------------------+
7 rows in set (0.01 sec)

and the index design window shows only column A as primary index,
ascending (unique checked), nothing else.

I assume this is a compatibility problem with the old server version...

Thank you anyways,
Marc