[jira] Resolved: (TUSCANY-3524) Issue with command caching in ChangeFactory

["Luciano Resende (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luciano Resende resolved TUSCANY-3524.
--------------------------------------

    Resolution: Fixed
      Assignee: Luciano Resende

Patch applied. Thanks Florian.

> Issue with command caching in ChangeFactory
> -------------------------------------------
>
>                 Key: TUSCANY-3524
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3524
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java DAS RDB
>    Affects Versions: Java-DAS-beta1
>            Reporter: Florian Pinel
>            Assignee: Luciano Resende
>         Attachments: TUSCANY-3524.patch
>
>
> In ChangeFactory.getCreateCommand() the create command is currently cached. This works fine if the command SQL is provided in the DAS config (table.getCreate()).
> However, when the command is generated from the passed data object, data may be saved incorrectly if 2 children are created, each with different properties set.
> A similar issue has already been fixed in ChangeFactory.getUpdateCommand(), by not caching the update command.
> I suggest that we modify getCreateCommand() and getUpdateCommand() to cache commands if and only if the command SQL comes from the DAS config.

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