[native] Change SQL errors log level.
- The SQL error itself is logged as 'info'.
- The 'transaction has been rolled back' message is logged as 'debug'.
These log entries should not be critical:
- If an error occur at the sql level, it will be transmitted as a CW error.
The exception is raised and handled in a higher level function, which will
decide if it is critical or not.
- Admitting that rolling-back automatically on errors is wanted in some
cases, it cannot be considered 'critical'. The caller will receive the
original exception anyway, it is its job to decide if it is critical or
not.
Closes #4801120
# copyright 2003-2012 LOGILAB S.A. (Paris, FRANCE), all rights reserved.
# contact http://www.logilab.fr/ -- mailto:contact@logilab.fr
#
# This file is part of CubicWeb.
#
# CubicWeb is free software: you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation, either version 2.1 of the License, or (at your option)
# any later version.
#
# CubicWeb is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
# FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
# details.
#
# You should have received a copy of the GNU Lesser General Public License along
# with CubicWeb. If not, see <http://www.gnu.org/licenses/>.
"""server side objects"""
import os.path as osp
def registration_callback(vreg):
vreg.register_all(globals().itervalues(), __name__)
global URL_MAPPING
URL_MAPPING = {}
if vreg.config.apphome:
url_mapping_file = osp.join(vreg.config.apphome, 'urlmapping.py')
if osp.exists(url_mapping_file):
URL_MAPPING = eval(file(url_mapping_file).read())
vreg.info('using url mapping %s from %s', URL_MAPPING, url_mapping_file)