Hi,
You should check your error logs for innodb errors, there will be the
key to the solution. If you want to avoid this behaviour, you can set
innodb=force in your configuration file to make innodb error fatal, or
set sql_mode to 'NO_ENGINE_SUBSTITUTION'.
Peter Boros
On 01/31/2011 08:21 PM, M. Rodrigo Monteiro wrote:
2011/1/31 João Cândido de Souza Neto<j...@consultorweb.cnt.br>:
I´m not so sure about that, but I think in MySql 3.23 the InnoDB engine was
disabled by default so you must be almost a PhD to enable it.
But the version of MySQL is 5.1 as you can see below...
What about updating server?
# cat /etc/redhat-release
CentOS release 5.5 (Final)
# rpm -qa | grep -i mysql
php-mysql-5.1.6-27.el5
MySQL-server-community-5.1.50-1.rhel5
MySQL-devel-community-5.1.50-1.rhel5
MySQL-client-community-5.1.50-1.rhel4
Regards,
Rodrigo.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
