On 04/20/2018 04:18 PM, Chapman Flack wrote:
> On 04/20/2018 04:03 PM, Andrew Gierth wrote:
>> Assign hooks aren't allowed to throw errors under any circumstance
>> because they're called during transaction abort, and throwing an error
>> during abort is obviously not tolerable.
>
> Ah yes, now y
On 04/20/2018 04:03 PM, Andrew Gierth wrote:
>> "Chapman" == Chapman Flack writes:
> Chapman> It seemed to me at the time to be not hard to implement, even
> Chapman> just as an extension for proof of concept. One small obstacle
> Chapman> is that the check hook on a variable doesn't get ca
> "Chapman" == Chapman Flack writes:
Chapman> It seemed to me at the time to be not hard to implement, even
Chapman> just as an extension for proof of concept. One small obstacle
Chapman> is that the check hook on a variable doesn't get called during
Chapman> attempted RESET, so the only
On 04/20/2018 09:55 AM, Matthias Kurz wrote:
> SET READONLY my_app.some_var = 'foo';
> SET READONLY SESSION my_app.some_var = 'foo';
> SET READONLY LOCAL my_app.some_var = 'foo';
>
> Of course read-only would default to false for backwards compatibility.
> When setting READONLY for on SESSION con
Hi,
in MS SQL Server you are able to make an entry of SESSION_CONTEXT read-only
by passing the @read_only param to the sp_set_session_context function:
"[ @read_only= ] { 0 | 1 } A flag of type bit. If 1, then the value for the
specified key cannot be changed again on this logical connection. If 0
