Re: DEFERRABLE NOT NULL constraint

From: Chris Angelico <rosuav(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: DEFERRABLE NOT NULL constraint
Date: 2013-02-06 09:22:03
Message-ID: CAPTjJmqNg0LPqtcRcgwOXpAoprjHmO2-w_hxVp=6LMO8Y1eZwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Feb 6, 2013 at 8:01 PM, Jasen Betts <jasen(at)xnet(dot)co(dot)nz> wrote:
> On 2013-02-06, Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben Madin 2013-02-06 09:28:36 Re: ERROR: invalid input syntax for integer: ""
Previous Message Jasen Betts 2013-02-06 09:01:06 Re: DEFERRABLE NOT NULL constraint