For now we rely on the default value set by python-sql but SQL-92 does not
define a default value.
Closes#12933
(grafted from 659160cd1681a6a1bc98d51a97d7765ee8d31714)
--HG--
branch : 6.0
The MemoryCache copy the stored template since 7bbbb91621ab but Genshi
Template clear the filters when copied.
Closes#12963
(grafted from 3111fe5130705da70e46b07e4b7cb47012430964)
--HG--
branch : 6.0
The cached values are copied when set and copied again when returned so the
stored values can never be modified.
Closes#9558
(grafted from 7bbbb91621ab3759dfdc04de3aa1754c89ef145d)
--HG--
branch : 6.0
Quite a few model have states with the same name (e.g. "open",
"close). When creating Workflow Graphs for several of these models at
once, the nodes of these states must be distinguished. Otherwise the
graphs will overlap and eventually even overwrite each other.
Closes#12253
(grafted from 91a09102ec61a08f57868bc9f030fdcb9ab831c8)
--HG--
branch : 6.0
When uwsgi forks workers it can happen that python execute the code from one of
the launched thread (eg: the cache listener or trytond-status). In that case
python will keep executing the thread and never switch to the main thread. Thus
preventing to listen for incoming connections.
Closes#12758
(grafted from d51b0990639d7ca0ac289dc08f56fd84a14e3e89)
--HG--
branch : 6.0
Each backend has their limit. 40 chars is picked as limit to match the size of
mercurial hash.
Closes#12754
(grafted from 3055098129d4afbf82af5fa527e3d3e357ea7021)
--HG--
branch : 6.0
The trailing zero are kept in the Decimal and rendered in the string
representation which is unexpected for a field with limited digits.
Closes#12587
(grafted from cfbc9e902c1d5f9bc299b536b495a98fda380369)
--HG--
branch : 6.0
If the target of the Reference field is deleted, the transaction cache is not
cleared because there is no "ON DELETE" support for Reference field. Instead
the ids are checked in the Reference.get method.
Closes#12599
(grafted from 7f25936732310704ad6296d5ab3f35e3276e2157)
--HG--
branch : 6.0
When there is no schema, the list values are not for a MultiSelection entry.
Closes#12417
(grafted from aedd6a22eabc62538664c0127739ac02acd8f429)
--HG--
branch : 6.0
Since 0db956eb2505 _changed_value is used for on_change_with calls, so it can
have to deal with unsaved Many2One value if it is the parent of a One2Many.
(grafted from 206e247e16437dc8b2f1989cc13b7e48a1d0dfc7)
--HG--
branch : 6.0
Like the one2many they should always be processed as they can have been
updated.
Closes#12474
(grafted from f45d89eb8048c28887d2e282a5dc7604bc8d9846)
--HG--
branch : 6.0
When a connection in the pool is disconnected, it stays in the pool and it may
still be served.
Using such connection raise an OperationalError and so the request is retried
but before that the connection is put back to the pool. So we may get it back
again.
It is not possible to distinct between an OperationalError due to a
disconnection or due to a isolation error for example.
So with the current design of Transaction API, an OperationalError always put
back the connection to the pool.
This main that we can only ensure that the connections served are still
connected by executing a simple query. And close connections that are failing.
Closes#12452
(grafted from f8aaf62a0c7508e3f3398e47dc2b86e6f8f06cc0)
--HG--
branch : 6.0
The rule must be enforced also when only non SQL type fields are read.
Closes#12428
(grafted from bd69f1025bca6648fd9ff11f585a60214d2bbf6e)
--HG--
branch : 6.0
If wrong variables are used to call gettext, the formatting may raise a
ValueError. It is better to not fail for such minor error when not testing.
Closes#12371
(grafted from 47809a507263c47b927c318750f22499adecd036)
--HG--
branch : 6.0
A call to clear_all is required after the commit in order to ensure that the
transaction uses an empty cache from this point. clear_all is not required to
prevent the deadlock on ir.cache because the rollback ensures that nothing
changed from the point of view of this transaction.
Close#12343
(grafted from 48396d9cfed6caccb3fca6d981fec5016a1f6ca2)
--HG--
branch : 6.0
Cédric Krier