Hi Steven,
<vendor>
IAS handles this for you. It supports writing only changed fields to
the database in CMPs.
Take a look at :
http://www.borland.com/devsupport/appserver/faq/Contract_for_Entity.html
and
http://www.borland.com/devsupport/appserver/faq/CMP_engine_details.html
</vendor>
> 1.) This email pertains to BMP EntityBeans
>
> 2.) All the examples I have seen pertaining to ejbStore have had an SQL
> statement updating on the database "every" field that is persistent
> within that EntityBean.
>
> 3.) I have not been able to find any alternatives to this all
> encompassing SQL statement; no arguments as to why you shouldn't design
> differently.
>
> 4.) I have a pre-EJB java framework that knows how to dynamically build
> SQL statements based on which "specific fields" are dirty.
>
> 5.) This email is not intended to discuss the use of a whole instance
> dirty flag (which I've seen discussed), but specific field level dirty
> flags (which I have not seen discussed).
>
>
> So my question is this:
> What would the implications be if my ejbStore knew that out of all 30 of
> my instance attributes, only one of the attributes was dirty and it
> generated an SQL statement that only updated that one field on the
> database for this one specific invocation of ejbStore?
>
>
> Steven E. Sobczak
>
>
===========================================================================
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".
