Hi Sheeri,
On 4 Aug 2009, at 22:27, Sheeri K. Cabral wrote:
On Tue, Aug 4, 2009 at 12:07 PM, Mark Leith<[email protected]> wrote:
On 4 Aug 2009, at 16:43, Brian Aker wrote:
Hi!
Just a quick note, the multi-table delete,update code was removed
from the
tree. This was in an early list and just never happened.
But:
1) It's extremely widely used
2) It's extremely useful and convenient *not* to have to do this in a
transaction
This is sad, imho. It also makes migrations of even the simplest
applications a lot more difficult..
Mark -- I agree with your 2 points, but I believe that
multi-update/delete isn't necessary if subqueries work properly and
efficiently. For example: DELETE FROM one_tbl WHERE stuff IN (....).
From what I see, multi-update and multi-delete are used to change
information in *one* table, but the rows to change are determined by
using more than one table. In that case, if/when subqueries work with
proper efficiency, the real issue of "I want to easily change
information in one table based on information in more than one table"
will be solved -- appropriately and non-buggily.
Have you found that multi-update/delete is used to actually change
information in more than one table? All the implementations of *that
usage* that I've seen in the wild have been instead of using foreign
keys and cascading properly.......
Yes I have - plenty. Foreign keys aren't in all storage engines.. ;)
Cheers,
--
Mark Leith
MySQL Regional Support Manager, Americas
Sun Microsystems, Inc., http://www.sun.com/mysql/
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
