Re: DEFERRABLE NOT NULL constraint - Mailing list pgsql-general

From Chris Angelico
Subject Re: DEFERRABLE NOT NULL constraint
Date
Msg-id CAPTjJmqNg0LPqtcRcgwOXpAoprjHmO2-w_hxVp=6LMO8Y1eZwg@mail.gmail.com
Whole thread Raw
In response to Re: DEFERRABLE NOT NULL constraint  (Jasen Betts <jasen@xnet.co.nz>)
Responses Re: DEFERRABLE NOT NULL constraint
List pgsql-general
On Wed, Feb 6, 2013 at 8:01 PM, Jasen Betts <jasen@xnet.co.nz> wrote:
> On 2013-02-06, B=E8rto =EBd S=E8ra <berto.d.sera@gmail.com> wrote:
>> Hi
>>
>>> You've hidden nothing from INSERT-RETURNING.
>>
>> ?? Or from a select, if the final value is what you mean. What we hide
>> is the way values are made, clearly not the final value. That bit is
>> accessible to anyone who can select the table, obviously.
>>
>
> so the trigger function is opaque, written in C or some other language
> where they can't access the source easily?

I still don't see how that's any better than a stored procedure that
directly does the INSERT. You can conceal the code every bit as
easily.

ChrisA

pgsql-general by date:

Previous
From: Jasen Betts
Date:
Subject: Re: DEFERRABLE NOT NULL constraint
Next
From: Ben Madin
Date:
Subject: Re: ERROR: invalid input syntax for integer: ""