Muly,
Yes the spec is written that way. But there is nothing that says your BMP
implementation can't cache the results of the initial query. Some BMP
generators <vendor> Cocobase </vendor> will write this code for you...
-Chris.
> -----Original Message-----
> From: Muly Oved [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, October 01, 1999 4:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Doubts about Entity beans, Should we use them?
>
> >If the original request was "Get me all employees", then the
> corresponding
> >find()
> >method in case of BMP might use one query
>
> >SELECT PKEY, FNAME, LNAME FROM EMP
>
> >to build the enumeration of primary keys AND entity bean for each
> employee,
> >which
> >will remain in cache until used by the caller.
>
> I don't think this can be done with BMP, as the result of the ejbFind
> should be an enumeration of primery keys, then the continer take every
> primery key and use ejbLoad to load the rest of the fields.
>
> The spec limit the way this find is solved, this is where CMP has more
> space for optimization.
>
> muly.
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
