[server] remove cnxset tracking, it is now unneeded
Indeed, all cnxsets will now be acquired using the following API::
with session.new_cnx() as cnx:
cnx.execute(...)
# do stuff
cnx.commit()
These well-scoped blocks are the only place a cnxset can be acquired.
The old use-case for un-delimited cnxsets (pyro/zmqpickle protocols)
have been removed.
The "mode" of connection objects becomes "write" forever (it will be
removed in a couple of changesets).
Related to #2919309.
/* styles for access control forms)
*
* :organization: Logilab
* :copyright: 2003-2010 LOGILAB S.A. (Paris, FRANCE), all rights reserved.
* :contact: http://www.logilab.fr/ -- mailto:contact@logilab.fr
*/
/******************************************************************************/
/* security edition form (views/management.py) web/views/schema.py */
/******************************************************************************/
h2.schema{
color: %(aColor)s;
}
table.schemaInfo td a.users{
color : #00CC33;
font-weight: bold;
}
table.schemaInfo td a.guests{
color: #ff7700;
font-weight: bold;
}
table.schemaInfo td a.owners{
color: #8b0000;
font-weight: bold;
}
table.schemaInfo td a.managers{
color: #000000;
font-weight: bold;
}
.discret,
table.schemaInfo td a.grey{
color:#666;
}
a.grey:hover{
color:#000;
}
.red{
color: #ff7700;
}
div#schema_security{
width:100%;
}