On Friday, January 17, 2003, at 11:08 AM, Jeremy Boynes wrote:
This leaves the JBoss-QL part read-only (it just qualifies the instances toI think we should support a full CRUD language. Specifically, I mean that the user should not be restricted to just specifying the WHERE clause, but they should be required to specify a DELETE clause also. Then we just put in a restriction that a remove method on the home interface is only allowed to remove entities of the current type. This is the same restriction finders have.
be deleted). We know we're deleting Transactions as the method would be on
the home interface for the Transaction EJB.
The reason I think we should have a full CRUD language is it allows an ejbSelect style method (although we may call it something else) to delete any set of objects with a single operation. This will be particularly useful to delete a subset of related objects.
-dain
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
