[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

     1

/var/log/cubicweb/*.log {

     2

        weekly

     3

        missingok

     4

        rotate 10

     5

        compress

     6

        delaycompress

     7

        notifempty

     8

        create 640 root adm

     9

        sharedscripts

    10

        postrotate

    11

           if [ -x /usr/sbin/invoke-rc.d ]; then \

    12

              invoke-rc.d cubicweb reload > /dev/null 2>&1; \

    13

           else \

    14

              /etc/init.d/cubicweb reload > /dev/null 2>&1; \

    15

           fi; \

    16

        endscript

    17

}