StrataFrame business objects have the ability to create a snapshot and then restore a snap shot of any contents of a BO. This can be done on a key as well and can be extremely useful.







The above code will save and respectively restore a snapshot saved off on a BO. You can do anything you like between the two and when you call the restore, the BO will be returned to its original state. Now this doesn't persist back to the database this way. If you are doing this during saves, then you need to use a transaction, which goes back to your original inquiry regarding a BO and transactions. If I am missing something, then please further explain what you are trying to accomplish.

Hi Taylor,

Could you please comment on this?

Kind regards....

Hi Taylor,

Can u suggest a way to implement savepoint issue in Strata Framework?

Or it is impossible?

Kind regards...

Hi Hector,

No, the transaction key relates to the transaction name, not a savepoint name. 

The difference being that passing a new transaction key from within strataframe would not create a new SavePoint within the existing transaction but, instead, would create a brand new transaction with the "transaction_name" being the StrataFrame transaction key.

So, in the MSDN online docs here, the StrataFrame transaction key relates to transaction_name | @tran_name_variable.

Trent L. Taylor (02/24/2010)

---

The transactions work the same across all databases in respect to how the framework interacts with the business objects and data access layer. So yes, this would be the same in SQL Server or Oracle.

Hi Taylor,

Let me put my question more clear since i know about transactional processing :

I wonder whether "transaction key" issue  corresponds to savepoint_varible in

the following (Transact-SQL) MS SQl Server command

SAVE { TRAN | TRANSACTION } { savepoint_name | @savepoint_variable } [ ; ]     ( MS SQL SERVER)

As you know same command in oracle is

SAVEPOINT <savepoint id>

I hope my question is more clear now.

Kind regards....

I must say that I use SF Transactions all over and they are in fact very flexible and extremely easier to setup and control.

Edhy Rijo

The transactions work the same across all databases in respect to how the framework interacts with the business objects and data access layer. So yes, this would be the same in SQL Server or Oracle.



If you are new to transactions within StrataFrame, then I would recommend taking a look at the docs as well. You can see more about using transactional processing in the help topic:







One thing to keep in mind with StrataFrame and transactions is that you can create as many simultaneous transactions as necessary and you can choose which BOs will be saved on what transaction using the transaction key specified by you, the developer. You can even save a BO off of the transaction while others are being save on a transaction. So transactional processing in StrataFrame is very flexible.

Hi Taylor,

Is this "transaction key" mechanizm same as "savepoint mechanizm in oracle or sql server"?

Can u explain little bit?

Kind regards...

No problem

Thanks for quick response.