Re: Database transactions and data-state flags


"Craig Buchanan" <someone@xxxxxxxxxxxxx> wrote in message
news:ui$CEcd$GHA.4892@xxxxxxxxxxxxxxxxxxxxxxx
Can you elaborate on now MTS would handle this? would the need for flags
be
removed? would each object need to handle its own persistence?

Thanks.

<snipped>


MTS would roll the update for both the Invoice and LineItems into one
Transaction. (which appears to be what you want)

Not sure what you mean by objects handling its own persistence. Did you mean
it can somehow destroy itself when its job is done? If so then you could
persist them with COM+ and recall, remove, execute as you saw fit from a
higher authority.

There really isn't enough information to go into detail - just wanted to
suggest that instead of rolling 'r own, you might want to use other
services.

COM+:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/html/b21a6b08-c17c-4fcc-bc60-39037bc9902f.asp

MTS:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cossdk/html/40eccce1-a362-4adc-8060-f6923b9162c9.asp

-ralph



.

Relevant Pages

  • Re: chooses not to generate code at all
    ... > The point is that one does not need persistence to do ... > transaction processing. ... That's why you would still need a DBMS event if you don't need ... Other simpler tools can handle persistence in business transaction ...
    (comp.object)
  • Re: CLOS and databases
    ... you get a transaction for every write no ... It also depends on whether you want to be able to rollback object changes. ... (setf object (make-instance 'persistent-user-class)) ... These are some of the fun problems persistence framework guys get to fight ...
    (comp.lang.lisp)
  • Re: Programming to an Interface
    ... the business logic in a transaction would be hidden at the next level down. ... in the above we must assume that Transaction.execute takes the object being modified and saves it to the DB while locking out any concurrent changes. ... Still, the code above says nothing about RDB, tables, rows, or anything else at all about the persistence mechanism. ... So the author has successfully avoided the implementation of the RDB and programmed to the interface of only the Account object, and the Transaction object. ...
    (comp.object)