Hi all!
Here's a question for all my fellow geeks / coders / software engineers
/ curious DB admins.
I've been doing a lot of reading lately, and have noted a few things:
1. Out of the "big three" commercial databases, only Oracle seems to
support nested transactions. Is there any practical purpose for such
things now that InnoDB has partial rollbacks? If there is a purpose for
such a construct, would implementing it hurt InnoDB's performance? I'm
not asking for the feature at all, I'm simply curious.
2. Reading up on MS SQL Server, the designers at MS seem to attribute
the speed of the product to three major factors:
* Their pool-of-threads architecture
* The fact that tables are locked as much as they need to be and no
more, with automatic lock escallation as required
(Database->Table->Page->Row)
* Optimistic Conflict Control
Obviously, the first of these is coming to MySQL eventually as listed in
the TODO pages. Would adding the second point to MyISAM be useful at
all, given the fact that we already have INSERT DELAYED? Would adding
the second point to InnoDB speed it up, slow it down or would the
benefits and pitfalls basically cancel each other out (Considering how
fast InnoDB already is, I've a feeling that this is not something that
would help performance)? As for Optimistic Conflict Control, this
wouldn't apply to MyISAM, would it? Seeing InnoDB include it would be
interesting, as Microsoft themselves have been a bit vauge as to the
integrity implications of this feature.
Please note: None of the above are feature requests! This is just one
guy's curiosity getting the better of him.
Regards,
Chris
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
