Hi! >Dear Mr. Tuuri, > > I think it is outstanding that you offer this essential add-in to MySQL.
Thanks! >Do you have any plans to add "On Delete Cascade" or "On Update Cascade" to >InnoDB, and if so when? I am still being forced to choose between sticking Sorry, not in the near future. But the multi-table DELETE which already is implemented in MySQL-4.0 does most of the job of ON DELETE CASCADE, you just have to call the SQL statement explicitly. Sinisa is writing a multi-table update which should do the job of ON UPDATE CASCADE. See the MySQL manual at http://www.mysql.com about the multi-table delete. >with Microsoft SQL Server or going to PostgreSQL in order to have these >features. Again, thank you, and the rest of the unbelievably generous >members of the MySQL open source community. I am continually awed by the >brain power laid on the table either in enlightened self interest or to >bring additional meaning and value to life. > >-Tom Schaefer Regards, Heikki http://www.innodb.com/ibman.html >""Heikki Tuuri"" <[EMAIL PROTECTED]> wrote in message >news:9rti5a$2pvv$[EMAIL PROTECTED]... > Hi! > >> MySQL/InnoDB-3.23.44 has been released for download at http://www.mysql.com >> InnoDB is a transactional table type of MySQL which supports row level >> locking, rollback, and other transactional features.> >> InnoDB is included in the MySQL-Max 3.23.44 binaries. The first binary >> download is the rpm for Intel x86. Solaris, Windows and other binary >> versions will roll out during the next 7 days. See http://www.innodb.com for >> more information. > >> * As the first table type in MySQL InnoDB features foreign key constraints >> which help to guard the integrity of your data. An example:> >> CREATE TABLE parent(id INT NOT NULL, PRIMARY KEY (id)) >> TYPE=INNODB; >> CREATE TABLE child(id INT, parent_id INT,> INDEX par_ind (parent_id), >> FOREIGN KEY (parent_id) REFERENCES parent(id)) TYPE=INNODB;> >> See the InnoDB manual at http://www.innodb.com/ibman.html for more >> information. > * DROP DATABASE now works also for InnoDB tables. >> * InnoDB now supports data files and raw disk partitions bigger than 4 GB on >> those operating systems which have big files. >> * InnoDB calculates better table cardinality estimates for the MySQL >> optimizer. >> * Accent characters in the default character set latin1 are ordered >> according to the MySQL ordering. >> NOTE: if you are using latin1 and have inserted characters whose code is > >> 127 to an indexed CHAR column, you should run CHECK TABLE on your table when >> you upgrade to 3.23.44, and drop and reimport the table if CHECK TABLE >> reports an error! >> * A new my.cnf parameter innodb_thread_concurrency helps in performance >> tuning in heavily concurrent environments. >> * A new my.cnf parameter innodb_fast_shutdown speeds up server shutdown. >> * A new my.cnf parameter innodb_force_recovery helps to save your data in >> case the disk image of the database becomes corrupt. >> * innodb_monitor has been improved and a new innodb_table_monitor added. >> * Fixed a bug in replication of auto-inc columns with multiline inserts. >> * Fixed a bug when the case of letters changes in an update of an indexed >> secondary column.> * Fixed a hang when there are > 24 data files. >> * Fixed a crash when MAX(col) is selected from an empty table, and col is a >> not the first column in a multi-column index. >> * Fixed a bug in purge which could cause crashes.>> Best regards,> > > Heikki Tuuri > Innobase Oy > 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
