D
dbeavon
Guest
I really appreciate the pointers. I don't suppose there are any docs about this stuff? I know that each database has its own local transaction, but beyond that it is just a matter of guessing how OpenEdge might coordinate the committing of them. Having a consistent outcome is the goal and it sounds like the DataServer technology does a good job to try and make that happen. It reminds me a little bit of the procedures we use to send a message out to the Sonic MQ broker at the very *end* of an OpenEdge DBMS transaction. We procedurally try to make sure that it happens right before the ABL's "END. /*TRANSACTION*/. And we also put some code before the beginning of the transaction to try to protect against the possibility that someone will one day wrap an even larger transaction around the whole mess, thereby circumventing the efforts to send/commit the Sonic message as the very last step. (IE. you can roll back the database transaction, but you can't un-send a Sonic MQ message after you've manually committed it). I don't suppose Progress could incorporate this Sonic ABL "commit" operation, and make it a function of the DataServer product too? I have always wished that ABL would coordinate the committing of our Sonic messaging operations. It would make me sleep better at night. 
Continue reading...
Continue reading...