At 2005-01-18 04:53, Craig Hoffman wrote:
I upgrade to 4.1.9 last night and I keep getting this error in PhpMyAdmin
after I changed the root password (yes I changed both pw's). Does anyone
have a solution on how to fix this? I'm running a Mac 10.3.x
#1251 - Client does not support authenticati
At 2005-01-17 15:12, shaun thornburgh wrote:
I am attempting to create a database and have a query. Is it possible for
mysql to contain the possible field values in the database rather than
creating the options in the application?
For example Field_A can only be Yes or No, Field_B can be 50% or
Please also note hat UPDATE returns the number of records updated. If your
UPDATE returns 0, you know that the record does not exist, and you might
want to INSERT instead.
At 2005-01-15 14:54, you wrote:
At 2005-01-15 14:48, you wrote:
Without using Select statement, how can I execute Insert SQL
At 2005-01-15 14:48, you wrote:
Without using Select statement, how can I execute Insert SQL statement if
Update action is failed?
I may be asking for too much. If Select statemnet have to be used to
determine the existence of a recordset, what is an efficient way to
execute Insert if Update is
g the data and then upgrading from 4.0 to 4.1(.8 or .9).
At 2005-01-14 11:35, you wrote:
Mattias,
please use
innodb_table_monitor
to print the contents of the InnoDB internal data dictionary.
http://dev.mysql.com/doc/mysql/en/InnoDB_Monitor.html
Regards,
Heikki
- Original Message ----- From:
/InnoDB_Monitor.html
Regards,
Heikki
- Original Message - From: "Mattias J" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, January 13, 2005 6:57 PM
Subject: Re: Upgrade correpted InnoDB tables
There are mostly just 2 or 3 corrupted tables out of about 100
e frm files. This will give you a fresh 4.1
table space to import into.
-Eric
On Thu, 13 Jan 2005 16:37:39 +0100, Mattias J <[EMAIL PROTECTED]> wrote:
> Earlier today we tried upgrading one of our MySQL servers from 4.0.15 to
> 4.1.8 using RPMs. This resulted in corrupted InnoDB
gs in the database (such as #3859, #3594, #3147) that talk
about similar symptoms. Are these problems in any way related to any bug?
Could we have done anything wrong during the upgrade (I did not perform it
myself)? What could we do to prevent this from happening when upgrading the
other servers?
