Roundup Tracker - Issues

Message6049

Author schlatterbeck
Recipients rouilj, schlatterbeck
Date 2017-11-04.10:11:44
Message-id <20171104101140.2w3ahyqh6v5e4g4p@runtux.com>
In-reply-to <20171104000529.BF65B4C0445@itserver6.localdomain>
On Sat, Nov 04, 2017 at 12:05:35AM +0000, John Rouillard wrote:
> 
> Umm, I thought raising reject in a reactor was useless? By the time
> the reactor runs the data is committed to the database.
No, this was never the case. Conceptionally the auditor runs before the
commit but if something fails in the reactor the change is still rolled
back.

> Right you expect a transaction that is either atomically applied
> across multiple tables/classes or rolled back. No split changes like
> you describe.
Yes. And this was the case until we added additional commit calls due to
otk handling.

BTW: I currently have a hard time writing a test for that :-)

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: office@runtux.com
History
Date User Action Args
2017-11-04 10:11:46schlatterbecksetrecipients: + schlatterbeck, rouilj
2017-11-04 10:11:46schlatterbecklinkissue2550955 messages
2017-11-04 10:11:44schlatterbeckcreate