Hi,

Llblgen pro 5.7.1RTM Adapter

I have jobs which track the progress of it's actions. These are mostly long running processes which post their (progress) state to the job. The job itself can be monitored and has info about start and end time, state, overall progress and of sub jobs.

Now I also need progress of the async commit of transactions. These can contain many inserts, updates and deletes in one transaction, and can last some minutes. I mainly use Entities which are tracked in a UnitOfWork2 or DataScope. And only sometimes plain Sql, but tracking these are only nice to have.

What options do I have to track the progression of the saves in the commit?

Thanks!

I think the same way as when using an adapter and not a unit of work: the adapter does the work. The unit of work allows you to obtain the queue lengths, and the # of elements to process, so you can calculate the total # of elements to persist/work on.

Then the adapter instance allows you to intercept when things have happened, e.g. in the OnSaveEntityComplete method for instance. This method is called after the entity has been persisted, also in an async scenario, so you don't run into the situation where the method returned but the work is still pending because it's async.

Thank you!

Is this possible to do with tracking stored procedure calls?

Otis wrote:

I think the same way as when using an adapter and not a unit of work: the adapter does the work. The unit of work allows you to obtain the queue lengths, and the # of elements to process, so you can calculate the total # of elements to persist/work on.

Then the adapter instance allows you to intercept when things have happened, e.g. in the OnSaveEntityComplete method for instance. This method is called after the entity has been persisted, also in an async scenario, so you don't run into the situation where the method returned but the work is still pending because it's async.

Is this possible to do with tracking stored procedure calls?

virginia wrote:

Otis wrote:

I think the same way as when using an adapter and not a unit of work: the adapter does the work. The unit of work allows you to obtain the queue lengths, and the # of elements to process, so you can calculate the total # of elements to persist/work on.

Then the adapter instance allows you to intercept when things have happened, e.g. in the OnSaveEntityComplete method for instance. This method is called after the entity has been persisted, also in an async scenario, so you don't run into the situation where the method returned but the work is still pending because it's async.

Is this possible to do with tracking stored procedure calls?

1) don't post in old threads so start a new thread next time
2) what are you trying to do/accomplish?

Otis wrote:

virginia wrote:

Otis wrote:

I think the same way as when using an adapter and not a unit of work: the adapter does the work. The unit of work allows you to obtain the queue lengths, and the # of elements to process, so you can calculate the total # of elements to persist/work on.

Then the adapter instance allows you to intercept when things have happened, e.g. in the OnSaveEntityComplete method for instance. This method is called after the entity has been persisted, also in an async scenario, so you don't run into the situation where the method returned but the work is still pending because it's async.

Is this possible to do with tracking stored procedure calls?

1) don't post in old threads so start a new thread next time
2) what are you trying to do/accomplish?

sorry about that. I have to show a progress bar for a unit of work commit containing hundreds of stored procedure calls. I was hoping there is some notification or event I could use to track the progress, like there is for entities

there might be, if you use Adapter. You can override the methods CallActionStoredProcedure and CallRetrievalStoredProcedure (or the async variants) and the proc call will end up in there, so you can use the override to e.g. send an event/message to your system to move the progress bar. That's about it tho, the Uow doesn't offer this ability as it executes the callbacks in a loop