Comments inline ...
Kelvin.
On 02/10/2007, Amita Vadhavkar <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Question in SDO -
> ChangeSummary changeSummary = root.getDataGraph().getChangeSummary();
> List changedDOs = commonj.sdo.ChangeSummary.getChangedDataObjects();
>
> is changedDOs an ordered list with order based on time of the change (i.e.
> if a user does a particular sequence of create, delete etc.
> is the sequence preserved in the changedDOs?)
A change summary describes the net effect of changes on the data
objects in the scope of the change summary since the point that
logging began. It doesn't reveal a full temporally sequenced change
history.
>
> Question in DAS -
> when das.applyChanges(root) happens with multiple changes, in
> Changes.execute() - DAS uses buckets of 1) insert, 2)update, 3) delete to
> fire the SQL statements in
> that order. Thus DAS does not attempt to preserve the order from changedDOs.
> As a result, even if a user has done delete(customer.id=1) and then create(
> customer.id=1), DAS
> attempts INSERT first and then DELETE and give SQL Integrity exception.
>
> If SDO change summary is preserving the order of changes, will it be better
> to propagate the same order in Changes.execute()?
>
> {Please refer to JIRA-1815 for some history.}
>
> Regards,
> Ammita
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
