Re: [JBoss-dev] no select-for-update with finder optimization(read-ahead)
Bill Burke wrote: > This is just as simple as modifying the getSql method in > JDBCLoadEntitiesCommand, correct? > Should be. -danch ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] no select-for-update with finder optimization(read-ahead)
This is just as simple as modifying the getSql method in JDBCLoadEntitiesCommand, correct? Thanks, Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of danch > Sent: Monday, June 18, 2001 3:17 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] no select-for-update with finder > optimization(read-ahead) > > > Ya, I realized I'd missed that right after I committed. If you want to > get that in there, go ahead. > > thanks, > danch > > Bill Burke wrote: > > > Danch, > > > > > > > > Great work on the finder optimization stuff. Our project really needs > > this feature for performance tuning. One thing you forgot I think, is > > adding select-for-update when doing your "select" for read-ahead > > finders. Is there any serious problem doing a select-for-update with > > read-ahead? We're using select-for-update to synch multiple instances > > of JBoss, so we can't use this new optimization until select-for-update > > can be enabled. If you see no problem, I can add this myself. Seems > > pretty straight-forward. > > > > > > > > Bill > > > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] no select-for-update with finder optimization(read-ahead)
Ya, I realized I'd missed that right after I committed. If you want to get that in there, go ahead. thanks, danch Bill Burke wrote: > Danch, > > > > Great work on the finder optimization stuff. Our project really needs > this feature for performance tuning. One thing you forgot I think, is > adding select-for-update when doing your "select" for read-ahead > finders. Is there any serious problem doing a select-for-update with > read-ahead? We're using select-for-update to synch multiple instances > of JBoss, so we can't use this new optimization until select-for-update > can be enabled. If you see no problem, I can add this myself. Seems > pretty straight-forward. > > > > Bill ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] no select-for-update with finder optimization(read-ahead)
Danch, Great work on the finder optimization stuff. Our project really needs this feature for performance tuning. One thing you forgot I think, is adding select-for-update when doing your "select" for read-ahead finders. Is there any serious problem doing a select-for-update with read-ahead? We're using select-for-update to synch multiple instances of JBoss, so we can't use this new optimization until select-for-update can be enabled. If you see no problem, I can add this myself. Seems pretty straight-forward. Bill
