Roundup Tracker - Issues


Author rouilj
Recipients rouilj, schlatterbeck
Date 2017-11-04.00:05:34
Message-id <20171104000529.BF65B4C0445@itserver6.localdomain>
In-reply-to <>
Hi Ralf:

In message
<> ,
Ralf Schlatterbeck writes:
>Ralf Schlatterbeck added the comment:
>I can finally reproduce this. When I have a web action with a handle()
>method like 
>    def handle(self):
>        cl = self.db.getclass(self.classname)
>        cl.set(self.nodeid, status = self.db.status.lookup("feedback"))
>        cl.set(self.nodeid, title = "Just a test")
>        self.db.commit()
>and we have an auditor (or reactor) that prevents the title change with
>a Reject exception

Umm, I thought raising reject in a reactor was useless? By the time
the reactor runs the data is committed to the database.

>then the first change (setting the status) will be committed. Note
>that the commit() in handle() is never reached because
>the second set() call will raise Reject.


>Note that the two changes above will not usually be for the same
>class (they could be combined into a single set call which is what
>the web-interface does when changing several values).

Right you expect a transaction that is either atomically applied
across multiple tables/classes or rolled back. No split changes like
you describe.
Date User Action Args
2017-11-04 00:05:35rouiljsetrecipients: + rouilj, schlatterbeck
2017-11-04 00:05:35rouiljlinkissue2550955 messages
2017-11-04 00:05:34rouiljcreate