Hi, readers of the mailing list!
I promised to report to the mailing list every week how the interfacing of
MySQL and the Innobase engine progresses. Innobase will provide transactions,
rollback, row level locking, and Oracle-style non-locking consistent read
to MySQL. It currently runs on Intel Linux and NT.
The following items from the TODO list from the last week have been done:
-------------
3. Give appropriate information to the MySQL query optimizer about
table sizes, and also to users about the file space occupied by each
table, index, and other data structures.
9. Prevent MySQL from using 'generate_table' in DELETE FROM ... . That
is not good if we want a rollback.
-------------
I am currently working on:
-------------
5. Add a timeout to lock waiting: Innobase can detect and resolve deadlocks
within its own lock table, but if a user uses also MySQL LOCK TABLES... or
BDB locks, a deadlock can occur where Innobase does not know of all the
locks: this is resolved by adding a timeout for a lock wait, say 100 s.,
after which the transaction is rolled back.
-------------
The following items remain:
-------------
2. Test correct handling of all MySQL data types and the SQL NULL value.
10. Port to Solaris, HP-UX and all different Unix flavors.
------------
>From the progress we can give an estimate that the interfacing will be done
2 weeks from now. I have available Linux-Compaq Alpha 64-bit and Solaris
32-bit platforms, for which the porting will be done. Then the source code
hopefully compiles and works on most other Unix flavors also.
Regards,
Heikki Tuuri
Innobase Oy
Helsinki, Finland
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
