I was thinking about something while looking at my application's
database behaviour... in many cases it is very inefficient to use a
finder method together with remove() for large collections. It would be
so much more efficient to have something like
public int deleteByCode(int code);
<deleter>
<method-name>deleteByCode</method-name>
<method-params>
<method-param>int</method-param>
<method-params>
<delete-method>
<ejb-ql>delete from Transactions t where t.code = ?1</ejb-ql>
</delete-method>
</deleter>
This all of course integrated with the cache so that it invalidates
objects that are already loaded, etc.
I'm just toying around with ideas here.
Stefan, wishes he had fulltime to work on things like this :-/
-------------------------------------------------------
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
- RE: [JBoss-dev] Finders, Selectors and ... deleters? Stefan Arentz
- RE: [JBoss-dev] Finders, Selectors and ... deleters? Jeremy Boynes
- Re[2]: [JBoss-dev] Finders, Selectors and ... del... Alex Loubyansky
- Re: [JBoss-dev] Finders, Selectors and ... delete... Dain Sundstrom
- RE: [JBoss-dev] Finders, Selectors and ... de... Bill Burke
- RE: [JBoss-dev] Finders, Selectors and ..... Jeremy Boynes
- Re: [JBoss-dev] Finders, Selectors and ..... Dain Sundstrom
- RE: [JBoss-dev] Finders, Selectors a... Bill Burke