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

Amita Vadhavkar resolved TUSCANY-1815.
--------------------------------------

    Resolution: Fixed

Changes applied under revision 588159

> das.applyChanges will always do insert instead of update if createDataObject 
> was used
> -------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1815
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1815
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java DAS RDB
>    Affects Versions: Java-DAS-beta1, Java-DAS-Next
>         Environment: DB2 Iseries
>            Reporter: Nick Duncan
>            Assignee: Amita Vadhavkar
>             Fix For: Java-DAS-Next
>
>         Attachments: 1815.patch
>
>
> If I do something like: 
> -------------------------------
>               DataObject root = das.getCommand("AllAutos").executeQuery();
>               
>               DataObject dao = root.createDataObject("t_test");
>               dao.set("NAME", "NICK");
>               dao.set("ID", 100);
>               
>               das.applyChanges(root);
> -------------------------------------
> There is already a row in the table with primary key 100.  ID is defined in 
> the config xml as being the primary key,  it ignores that ID was set and does 
> an insert statement.  ID is also defined as an auto generated column.
> Basically I was expecting something like Hibernate's savorOrUpdate...   Maybe 
> if the field that represents primary key  is shown to have been changed in 
> the changeSummary, then  DAS will figure out what statement to generate.  
> Where I'm seeing this being a problem is if we get a dataobject that 
> represents a row in the database, and then send it off to a service, we get 
> back another object that has been updated, but since it is a different object 
> then the DAS will think it should do an update?  Merge doesn't  seem to  
> alleviate this problem either.  Please let me know if I am way off base here. 
>  Thanks

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to