Even if the backend allows NOTIFY query on readonly transaction, it is strange
to commit readonly transaction because the backend may not enforce the
readonly.
Also commit performs other actions that may not be wanted like commit
datamanager or clear cache.
A procedure that requires to perform a NOTIFY should have a non-readonly
transaction.
Closes#12542
(grafted from 03611153e9bc9a0d169447c4ca946ad49c81ad47)
--HG--
branch : 6.0
If user_id is accessed before view_args has been setup, we should not cache
`None` as value but instead raise an exception.
The `user_id` may be accessed before the mapping if the request is logged
because the representation of the request used the `rpc_method` which needs to
parse the request data. But since 1923117e935d parsing compressed content is
only allowed for request with `user_id`.
So we can no more include the `rpc_method` is the request has not yet been
mapped and so it has a `view_args`.
Closes#13203
(grafted from 0630029c1d5a0a2c7bd45086957f2e0fbed4c427)
--HG--
branch : 6.0
The Function fields are not copied so it is the storage field that must have a
default value.
Closes#13170
(grafted from 96d629fe11a710b395d9981881c5dfda1674becf)
--HG--
branch : 6.0
The commit call was added by a6624f31ff20 to release lock because Cache.resets
was called inside the transaction.
But Cache.resets was removed in a83631f4ba67 and Cache does not create any new
transaction since.
And since 2fd8c5f88265 the transaction is even committed only on module
update.
(grafted from 0548d73c7ce3b4e07b6b76007f2592ed2be945ff)
--HG--
branch : 6.0
Decimal may raise an InvalidOperation error if the context does not allow the
needed precision.
But rounding is not necessary for Decimal as we can just test the exponent
from the tuple version.
Closes#13138
(grafted from 776889be97e4c1b8917a9090338511d8008c625b)
--HG--
branch : 6.0
A Pool.refresh may be triggered on Pool.init if a cache listener is started by
the new transaction of load_modules. In such cache the pool is empty just
after the init.
Closes#13101
(grafted from 4c210ce062018f7021c2ac5328d558ca8e9899fa)
--HG--
branch : 6.0
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
Cédric Krier