doc/book/admin/rql-logs.rst
author Denis Laxalde <denis.laxalde@logilab.fr>
Thu, 14 Mar 2019 14:38:55 +0100
changeset 12500 ef2168f389f6
parent 10491 c67bcee93248
permissions -rw-r--r--
[test] Remove upper bound for cubicweb-localperms Version 0.4.0 does not use a deprecated API that we are planning to drop in forthcoming changesets. This requires changing expected values in unittest_cwconfig.py where we scan install cubes. * In CubicWebConfigurationTC.test_available_cubes(), localperms disappears from the list of expected cubes because this test method will look for new style cubes in located in cubicweb/test/data/libpython/ (we patch pkg_resources.iter_entry_points()) as well as old style cubes installed in $PREFIX/share/cubicweb/cubes; since the new cubicweb-localperms version is new-style, it won't be catched by this method. * In CubicWebConfigurationWithLegacyCubesTC.test_available_cubes(), localperms is still listed, but now with the package name, because this method will simply look at installed cubes whether old or new style.

.. -*- coding: utf-8 -*-

RQL logs
========

You can configure the *CubicWeb* instance to keep a log
of the queries executed against your database. To do so,
edit the configuration file of your instance
``.../etc/cubicweb.d/myapp/all-in-one.conf`` and uncomment the
variable ``query-log-file``::

  # web instance query log file
  query-log-file=/tmp/rql-myapp.log