Since Werkzeug >= 2.3, it always tries to parse the Authorization header as a
digest. If the session value which is encoded in base64 needs padding, the
trailing `=` are interpreted as header values and the token attribute is not
filled.
In this case we must parse ourself the Authorization header to decode the
base64 value as session.
Closes#12259
The changeset 2763339d88d5 removed the fallback when reading invalid data for
a selection but it is important to not fail on reading to let the user fix the
error.
Since c8771e45b861 an exception is raised if the table was not locked on
transaction starts.
When validating some records with trytond-admin, we do not want to restart the
validation process to lock the tables to avoid creating conflict with the
running server.
As the cache is rollback to avoid dead lock, the transaction commit could
restore cache version that is no more valid.
For example the language cache of `ir.translation` which is filled initially
with only English and then reset when other languages are created by the `ir`
module. So at the end of `ir` module load, the cache is reset to contain only
English as it was the content before the first cache reset. This prevents to
load any other language from other modules.
So to ensure the next module is loaded using a fresh cache, all the caches are
cleared.
Closes#12246
There is no guarantee by SQL standard that the order of the returned values of
INSERT are the same as the order of VALUES.
Also there is neither any guarantee that the generated id follow the order of
VALUES but the ORM relies on such order to keep records ordered in the same
order as the user insert them (and also for sequence order with NULL value).
So for database that supports multirow insert, we need to set explicitly the
value for the column id to ensure to preserve the insert order.
Closes#12220
The sequence functions are using string parameters so for case sensitive
sequence name we must pass a string containing double-quoting if necessary.
Closes#12194
When the reference field is validated (without check access), it should not
fail for SelectionValidationError if the user has no access to the resource.
Closes#12178
The migration introduced in baa87cf1a343 would fail because previous migration
would have wrongly set a default value in id column of history tables
Closes#12186
It logs by default:
- the write and delete done directly by the users
- the execution of a button
- the execution of wizard state that has modified the database
- the workflow transition to a new state
Cédric Krier