----- Original Message ----- From: José Ostos Turner <jos...@spin.com.mx> To: <mon...@tcx.se> Cc: <win...@lists.mysql.com> Sent: Wednesday, October 13, 1999 11:20 AM Subject: RE: Several problems

"MySqld" does not recognize the option --flush. The problem appears to be the file size not being updated. I will try to see what happens with the command 'mysqladmin flush-tables'. I could put a program (schedule) that automatically runs this command every so often, but is there a problem with this if the database is being used by another connection?

Simply as a doubt, Is it not possible for MySql to detect when a table has been updated and to close it automatically as soon as there are no connections actually using the table?

Another question that comes to mind is with regard to the physical files. If I copy all the files of a given table (*.frm, *.isd, *.ism) from one database directory to another. The table sometimes does not appear in the database (sometimes it does). This happens even if I shut down the server, the computer and restart everythimg. However, all querys done on the table work just fine. The problem is if I want to use a query builder (through ODBC), I can't use the table because it does not seem to be in the database. What can I do so that MySql recognizes the table in the new database.

As a comment: The "Views" or "Subquerys" are features that are quite indispensable and very hard to work around in some cases. I know that this is somewhere in the TODO list, but when are these changes expected to be actually working, especially in the Win32 environment.

Regards Jose Ostos

Hi!

The shareware version has 2 known problems; ALTER TABLE and when using LOCK TABLES in some cases, but as either bug isn't that important when evaluation MYSQL, we haven't put a lot of time into fixing this. We will however probably update the shareware version to a newer one when MySQL 3.23 gets stable.

Anyway; All CREATE TABLE, UPDATES and ALTER TABLES should be commited at once. If you can produce a test that shows that this is not the case then we would be very interested in looking at this!

One problems on Win32 is that even if MySQL writes everything to disk between each SQL statement, the file size is not updated (this is a bug in the design of Windows). This means that if your computer crashes you may loose the rows you inserted since you started mysql if you don't run isamchk on the tables before you start using these again! You can force MySQL to close all files (and thus update the file size) by executing 'mysqladmin flush-tables'.

The registered version will automaticly close all files every 30 minutes (this is a startup parameter) to avoid this problem. Another possibility is to start mysqld with --flush. In this case MySQL will do a extra system call between each update to update the file size. The major problem with this is that its makes MySQL much slower!

Regards, Monty