Am Dienstag, den 19.07.2005, 13:00 +0200 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
>
> > No, no index but the primary key defined, values 1-18 in the table,
> > trying to insert 20, 111 or something.
> > ....
> > and the index design window shows only column A as primary index,
> > ascending (unique checked), nothing else.
>
> Strange then.
>
> > I assume this is a compatibility problem with the old server version...
>
> Sounds like this. Not sure if the deeper reason is on OOo or MySQL side
> ("compatiblity problem" still leaves both options, even if OOo
> collaborated perfectly with the other server version). But I'd guess I'd
> blame MySQL, since the exception message really sounds like a problem of
> either the server or the driver.
I think it is. In the meantime I went digging my backups for the old
"org.gjt.mm.mysql.Driver" and this one does in fact work. But the last
test for conn/j is standing out: using fully qualified table names, I
*think* I did not use them...
> Do you have a chance to temporarily switch to ODBC and see if the
> problem persists?
No I can't, the support for the old 2.50 MyODBC has run out. I'd have to
fiddle the libraries and their dependancies in manually, which I'll not
do. Planning for upgradfing the server has started (btw. it wouldn't if
these problems did not arise ;).
On last question: for being consevative, what version of MySQL is best
know and supported from the OOo-side? I'm tending to use 4.x, I only
wonder if 4.0 or 4.1 is best...
Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
