Andrew, unfortunately it usually takes 7 days for the Windows binary to appear.
Regards, Heikki ----- Original Message ----- From: "Andrew Chan" <[EMAIL PROTECTED]> To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, April 23, 2002 8:43 PM Subject: Re: Prerelease of MySQL/InnoDB-3.23.50 > There is no download for Windows at the moment, isn't it? > > Andrew > ----- Original Message ----- > From: "Heikki Tuuri" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, April 23, 2002 1:12 PM > Subject: Prerelease of MySQL/InnoDB-3.23.50 > > > > Hi! > > > > InnoDB is a MySQL table type which adds transactions, row level locking, > hot > > backup capability, and foreign key constraints to MySQL. > > > > Version 3.23.50 of InnoDB features an auto-extending data file, better > > support for InnoDB Hot Backup, and better support of foreign key > > constraints, including ON DELETE CASCADE and ON DELETE SET NULL clauses. > > > > InnoDB is included in the MySQL-Max-3.23, MySQL-4.0, and MySQL-Max-4.0 > > distributions of MySQL. For more information about InnoDB see the online > > refererence manual at http://www.innodb.com. > > > > Since MySQL-3.23.50 was compiled with a new glibc and a new compiler on > > Linux, MySQL AB decided to give out a prerelease before moving it to the > > regular downloads page. You can now find 3.23.50-pre at the following > link: > > > > http://www.mysql.com/downloads/mysql-3.23-pre.html > > > > > > Changelog of MySQL/InnoDB-3.23.50, April 23, 2002: > > > > * InnoDB now supports an auto-extending last data file. You do not need to > > preallocate the whole data file at the database startup. > > > > * Made several changes to facilitate the use of the InnoDB Hot Backup > tool. > > It is a separate non-free tool you can use to take online backups of your > > database without shutting down the server or setting any locks. > > > > * If you want to run the InnoDB Hot Backup tool on an auto-extending data > > file you have to upgrade it to version ibbackup-0.35. > > > > * The log scan phase in crash recovery will now run much faster. > > > > * Starting from this server version, the hot backup tool truncates unused > > ends in the backup InnoDB data files. > > > > * To allow the hot backup tool to work, on Windows we no longer use > > unbuffered i/o or native async i/o; instead we use the same simulated > async > > i/o as on Unix. > > > > * You can now define the ON DELETE CASCADE or ON DELETE SET NULL clause on > > foreign keys. > > > > * FOREIGN KEY constraints now survive ALTER TABLE and CREATE INDEX. > > > > * We suppress the FOREIGN KEY check if any of the column values in the > > foreign key or referenced key to be checked is the SQL NULL. This is > > compatible with Oracle, for example. > > > > * SHOW CREATE TABLE now lists also foreign key constraints. Also mysqldump > > no longer forgets about foreign keys in table definitions. > > > > * You can now add a new foreign key constraint with ALTER TABLE ... ADD > > CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...). > > > > * FOREIGN KEY definitions now allow backquotes around table and column > > names. > > > > * MySQL command SET TRANSACTION ISOLATION LEVEL ... has now the following > > effect on InnoDB tables: if a transaction is defined as SERIALIZABLE then > > InnoDB conceptually adds LOCK IN SHARE MODE to all consistent reads. If a > > transaction is defined to have any other isolation level, then InnoDB > obeys > > its default locking strategy which is REPEATABLE READ. > > > > * SHOW TABLE STATUS no longer sets an x-lock at the end of an > auto-increment > > index if the auto-increment counter has already been initialized. This > > removes in almost all cases the surprising deadlocks caused by SHOW TABLE > > STATUS. > > > > * Fixed a bug: in a CREATE TABLE statement the string 'foreign' followed > by > > a non-space character confused the FOREIGN KEY parser and caused table > > creation to fail with errno 150. > > > > Best regards, > > > > Heikki Tuuri > > Innobase Oy > > [EMAIL PROTECTED] > > http://www.innodb.com > > > > > > > > > > --------------------------------------------------------------------- > > 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 --------------------------------------------------------------------- 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
