G T Smith wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SuSE 10.2
Did an update today including MySQL security updates.
Found MySQL had failed to reload for some reason.
Restarted MySQL and got a a duplicate column error message when an
attempt to update the mysql database tables was applied. (unfortunately,
error message went before I could take notes and nothing in logs).
Nothing seems to broken but unable to repeat error (I suspect because
the database schema update has now been flagged as applied).
Because there is an issue with funambol I am running MySQL with case
sensitivity disabled...
As I do not think this is a change applied at the MySQL end (the mysql
schema is reasonably consistent across platforms and if this is a case
of two columns differing by case this it would generate problems on
Windows) I am not sure whether the update has been applied a second time
for some reason (then I need not worry) or there has been a change and I
should have two columns lexically differing only on case or replaced.
Has anyone noticed anything similar?
Yes, I noticed that mysql was dead after the last upgrade on my suse
10.2/64 server, and a bit of lookikng in the the mysqld log turned up a
complaint about a duplicate column IIRC - but I started it with the rc
script and it has run normally from that point on, so I hadn't give it
too much further thought.
Joe
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
