[dbapi] refactor so that cw 3.8.6 can still speak with a 3.8.5 server

cleanup

[bfss] fix file update to ensure file's content is available on the fs asap... and not only at commit time. So it's consistent with entity creation behaviour. The new file is created at assignement time and removed if the commit is rollbacked.

[ldap] fix exception handling on authentication error

[ldap] cleanup password checking

cleanup

[css] make body bg color configurable

bump version number to trigger migration

3.8.6

[migration] schema should be accessed through .repo

backport stable

[security] use set_operation for relation permission checking operation

[migration] refactor schema migration fix introduced by 5833:d7256ae7c1d1 so the code looks better and avoid clutering lgdb api. Depends on lgdb 1.0.5.

[schema migration] fix name error introduced in parent changeset

[schema migration] avoid potential duplicated ft reindexation due to multiple UpdateFTIndexOp operations by using set_operation

[sql generation] fix bug with inlined relation and referenced by other neged relation we should check in that the column is not null in such cases

[refactor] refactor rtag keys generations.

[fix] fix a uicfg bug in autoform_section When several rtags matches the same relation (for example "* login *" and "CWUser login *") inconsistent rtag could be merged.

[debian] fix logrotate error introduced by 5806:9ef0e95f4d2b: sh don't want spaces here

[debian] fix logrotate error introduced by 5806:9ef0e95f4d2b: sh don't want spaces here

cleanups

[login form] fix bad login field label by using pgettext

updated docstrings on Operation class

do not allow password-less bind: windows accepts this as Anonymous Logon

[#969169] don't display remove link in edition forms if the cardinality is 1

fix name error

fix schema migration hooks (partial) SQL Server requires some additional steps to alter columns (index drop and restore, etc...) and this in turn requires passing a connection on the DB to find out the indexes. Also partially fix an issue where the null_allowed value was not correctly computed. Still some problems in there (see https://www.logilab.net/cwo/ticket/1109558)

delete trailing whitespace

Had thought this could be done in cube, but it really needs to be done earlier in the migration process

EntityFormRenderer redefine open_form and add a div section, so redefine close_form to add the closing div tag

Backed out changeset c29c90223125 which breaks the cw tests

EntityFormRenderer redefine open_form and add a div section, so redefine close_form to add the closing div tag

reduce log verbosity in ldapuser source

[session] refactor session handling so that when calling session.close(), pool of long running transaction of the same session is properly freed

[debug views] set http cache max age to 0 on debug views

cleanup

[schema view] width isn't in authorized th attribute in xhtml DTD. katia, please do it another way.

[schema view] fix typo

[rql2sql] #1089207: do not encode Unicode strings from RQL statements to db encoding

fix bad merge

[css] more css rework, need visual test in compat/new modes

backport stable

[config] fix dumb name error

[form] apply patch #933771: format_single_value / vocabulary methods should *always* return actual value as an unicode string

backport stable

[repo] fix 'c-c start --loglevel LEVEL' for repository only configuration. Closes #1058269.

[transaction w/ separated web/repo processes] the dbapi should explicitly specify a transaction id to avoid confusion when web server / repository run in separated processes

[dbapi] Connection.load_appobjects should load site_cubicweb files as well, they may contains necessary RQL extension function definitions. Also kill some broken deprecated code in this method.

backport stable

Added tag cubicweb-debian-version-3.8.5-1 for changeset 5d05b08adeab

Added tag cubicweb-version-3.8.5 for changeset 2de32c0c293b

[repo] call entity.check() once before_update hooks has been called, to let them a chance to transform data

3.8.5

[debian] #1027463: logrotate script should filter out warnings

[schema migration] fix fix introduced in 5803:589e2e3fb997, test for backend alter column support should be done in the operation, else the associated index is not dropped while this is supported

[schema migration] fix backend compatibility issue by using type_from_constraints / sql_change_col_type instead of bare ALTER COLUMN

[schema migration] don't try to drop column if backend doesn't support column alteration (eg sqlite)

[session] when rollback_on_failure is false, we should not try to reconnect if the sql raised an error

Use SQL standard ALTER TABLE command (with ADD instead of ADD COLUMN)

reduced logging verbosity in ldapuser source