It will just be built underneath existing functionality like delete(query) and orphan delete. It will support all Hibernate semantics. So this:
session.delete("from Foo foo where foo.name like 'foo'")
will cause two queries:
SELECT ... FROM FOO WHERE NAME LIKE 'foo' DELETE FROM FOO WHERE NAME LIKE 'foo'
ok - so instead of deleting one at the time, we batch delete, but still call all the lifecycle stuff ?
(but isn't the users just going to ask for a quick batch delete instead then (to avoid the possible expensive delete ? ;)
/max
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
