On Thu, Feb 25, 1999 at 08:59:56AM -0800, Mike Chu wrote:
> A primary key is based on fields which can be updated. Does this
> mean the pk could change once these fields change?
> This is a problem with container managed beans only, IMHO - because
> primarily due to implementation.
> Here in Hong Kong we don't have too many implementations. Would
> appreciate a reply from more knowledeable American (yankee!!)
> friends.
> -mc
>
[Hi folks, good to be back.]
Well I'm not an American, but I do have something to add.
Primary key fields are public so that the container can set them after
ejbCreate has finished. It needs access to them during updates as
well. However, you would certainly never want to change the values in
the PK yourself. It's difficult to see how the specification could
enforce this, and yet still allow containers access. It's difficult,
but I'm sure not impossible.
Until then, you just have to try to avoid changing pk fields in your
code.
This one's up for discussion.
Malcolm
===========================================================================
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".
