Hello, > MyODBC 3.51 is the only way that I access the database. (MyODBC is used in a multithreaded server and in >InternetInformationServer (asp)) >The server is coded in c++ and got a class that acts like a odbc pool (keeps connections open during the lifetime of the server >and handles them to threads that requests a db connection)
It may help to know more about the work of features (multithreaded server, 'odbc pool') you are using with MySQL. I have only one vague idea it above. I know that MySQL is multi-threaded (it may have many queries on the same table simultaneously). Remarks that keeps connections open during the lifetime of the server and handles them to threads that requests a db connection SHOULDN'T be the culprit of table crash. In contrary this is a good thing; PHP, that i used, do the same job with the feature of PERSISTENT CONNECTIONS. Also the version of MyODBC (MyODBC 3.51 ) you are using is declared STABLE by MySQL , though MySQL says : 'some issues brought up appear to be application-related and independent of the ODBC driver or underlying database server. > How are tables getting unclean? Has many ways like : - the mysql daemon server stops in a abnormal way , you can see it in the mysql error log file - a query fail to continue processing - a system problem > When are tables closed? A table is opened for each concurrent acces, A table is closed when the connection using them is closed / lost Regards Thierno6C - MySQL 4.0.15 ----- Original Message ----- From: "Datatal AB - Gauffin, Jonas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 07, 2003 10:05 AM Subject: SV: Table crashes Hello > crashes occurs for some reasons like : > - unclean tables ( tables are closed improprely), > - hardware problems > - something goes wrong in the system > - know bugs > Check that your tables are clean, before start using them. MyODBC 3.51 is the only way that I access the database. (MyODBC is used in a multithreaded server and in InternetInformationServer (asp)) The server is coded in c++ and got a class that acts like a odbc pool (keeps connections open during the lifetime of the server and handles them to threads that requests a db connection) How are tables getting unclean? When are tables closed? Should I disconnect/connect when a thread is handling the dbconnection back to the pool? > It seems that you said the REPAIR doesn't occurs after you > configuring related variables in the my.cnf file ? Because > the daemon will not start when the my.cnf contains any errors > (variable names), the format is to be correct. No. I asked if my configuration were correct. I've just added it to my.cnf. > Can you indicates what MySQL version you run and your OS version. Win2000 Mysql 4.0.12 (mysqld.exe) MyODBC was an old version (2.x), I've just installed 3.51.06 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
