db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-163) Platform Update Behavor should not set to NULL not defined properties of a DynaBean
Date Thu, 15 Mar 2007 16:02:09 GMT

    [ https://issues.apache.org/jira/browse/DDLUTILS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481199

Thomas Dudziak commented on DDLUTILS-163:

The problem is that in the extreme case (which properties are undefined varies from dyna bean
to dyna bean) for each bean a new prepared statement has to be created which in turn renders
batch mode useless and means a huge performance impact. 

> Platform Update Behavor should not set to NULL  not defined properties of a DynaBean
> ------------------------------------------------------------------------------------
>                 Key: DDLUTILS-163
>                 URL: https://issues.apache.org/jira/browse/DDLUTILS-163
>             Project: DdlUtils
>          Issue Type: Improvement
>          Components: Core (No specific database)
>         Environment: All environements
>            Reporter: Lucas Moreno
>         Assigned To: Thomas Dudziak
> The default update behavor implemented in PlatformImpl takes a DynaBean as parameter
and creates a UPDATE statement for all the columns of the table nor only those ones defined
as properties of the bean.
> The result is that not specified properties of the bean are set to NULL which may no
be the desired behavor.
> An update using a DynaBean should only update columns wich have a value (also null) 
for a given property.
> As I see, the update method should:
>  - Check that all the primary keys are defined in the bean
>  - Prepare a SQL Update query only with the values specified in the  bean
>  - Execute the update

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message