Discussion (7)1
Log in or sign up to continue

Hello Jack,

I have done this previously in this class:

Class User.OperationSQL Extends Ens.BusinessOperation

{

Parameter ADAPTER = "EnsLib.SQL.OutboundAdapter";

Property Adapter As EnsLib.SQL.OutboundAdapter;

...

I have this code to begin transaction:

set tSC = ..Adapter.SetAutoCommit(0)

I have this code to commit transaction:

set tSC = ..Adapter.Commit()

In case of rollback I use this code:

Set rollbackSt = ..Adapter.Rollback()

lol, reading is fundamental.  Thank you for pointing out what should have been obvious.

I missed the "User" in your example as a custom implementation.  I just reviewed these provided adapters, very nice!  What continues to puzzle me is why the product does not provide a Business Operation off them (and others).  I know, support issues, right?

I just completed a custom "adaptation" using their provided Util.Pipe adapter, because the code was a bit crusty.  It did serve as nice reference source, just not as nice as these SQL adapters.

Can you expand upon your question a little more?  I just posted an article for sending message data to an external SQL database -- but by invoking a Stored Procedure (not SQL inserts or transactions), which I find eminently better to keep that business logic out of the messaging bus.

https://community.intersystems.com/post/ensemble-operation-calling-sql-s...