Daniel OConnor wrote:
>
> On 3 Aug 01, at 17:21, Ian McCallion wrote:
>
> > Cedric, if I understand correctly, field groups are a means of eager-loading one
> > field when another is accessed. So this does not really get to the heart of the
> > matter any more than Dominic's suggestion of using BLOB in the database. There'd
> > still be n-1 SQL calls instead of 1.
>
> Hi Ian,
>
> I implemented your problem (with the caveat that ejbSelectByDate can use
> a data range) and posted the code to
> http://www.mvcsoft.com/fault_group_example/intro.htm. It also includes a
> quick-and-dirty Swing test client.
<snip>
> This was relatively straightforward using the mapping tool included with the
> persistence manager, and works without any proprietary code in your EJB
> 2.0 JAR. Is it basically what you wanted to accomplish?
Daniel, thanks for the solution, which as you say is a completely portable
solution and is perhaps what the EJB architects were thinking of when limiting
ejbSelect in the way they did.
I'm uncomfortable about it for two reasons though:
1. Such extreme "optimization" is effectively proprietary
function - the code may port to another server but the
application as a whole wouldn't (for performance
reasons)
2. Extreme optimizations are like extreme sports - you can
be in big trouble if things go even slightly wrong!
I could imagine spending lots of time regaining the
performance after every minor change to the application
or middleware. Getting it to work may be very satisfying
to the technologists, but is the way to run a business?
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
