It might be worth elaborating on this a little more in the documentation
and/or book. Feel free to use any of the above.
We have a draft that touches on the transactions at the end:
https://github.com/bestpractical/rt/blob/4.0/add-rt-crontool-docs/docs/automating_rt.pod
It's not exhaustive
On 07/16/2013 08:48 PM, Craig Ringer wrote:
> They're not related to database-level transactions since RT doesn't make
> use of them.
This is wrong. RT _does_ make use of DB transactions. grep for
BeginTransaction and/or Rollback.
> It looks like --transaction picks an *existing* transaction to
I've taken a look at the RT Book, the rt-crontool docs
http://bestpractical.com/docs/rt/latest/rt-crontool.html and the Wikia
article http://requesttracker.wikia.com/wiki/UseRtCrontool and haven't
been able to find an explanation of what exactly the transaction options
mean and control.
They're no
