[server/session] Roll back in connection exit
This was changed in commit 8b35a898b334 "[server] remove cnxset
tracking, it is now unneeded".
When exiting a CubicWeb Connection, the database connection is put back
into the common pool. At that point anything done during the lifetime
of the CubicWeb Connection needs to be committed or rolled back.
Do a proper rollback to finish the transaction, as was happening before
the above-mentionned commit.
This showed up on testing with postgresql, when a DB schema modification
was blocked by an old connection that was still "in transaction".
.TH cubicweb\-ctl 1 "2010-01-14" cubicweb\-ctl
.SH NAME
.B cubicweb\-ctl
\- cubicweb control utility
.SH SYNOPSIS
.B cubicweb-ctl <command>
[
.I OPTIONS
] [
.I <command arguments>
]
.SH DESCRIPTION
.PP
CubicWeb utility to create and control instances, and more generally do all
cubicweb's related tasks you can have to do using the command line. Available
commands will depends on which part of the framework are installed.
.PP
Type
.B "cubicweb\-ctl <command> \fB\-\-help\fR"
for more information about a specific command.
.SH COPYRIGHT
Copyright (c) 2003-2010 LOGILAB S.A. (Paris, FRANCE).
http://www.logilab.fr/ -- mailto:contact@logilab.fr