Re: Check constraints and function volatility categories

On 02/01/2016 12:52 PM, Dane Foster wrote:
> On Mon, Feb 1, 2016 at 3:41 PM, Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>

>
>     As an example of where this leads see:
>
>     http://www.postgresql.org/message-id/7224.1452275604@sss.pgh.pa.us
>
> ​Thanks for the heads up. The good news is all machine access to the
> data will be via functions and views so I can inline the constraint in
> the right places. In other news, this sucks! I have no idea what it

I could see moving your constraint into a per row trigger.

> would take to implement a more flexible constraint mechanism where these
> types of dependencies can be expressed declaratively but it would be
> great if someone w/ the know-how did. As is evident by the fact that I
> wasn't the only one to not realize the rabbit hole I was heading down,
> it would be a useful feature.
> ​
> ​As always thanks for setting me straight,
>
> Dane
>


--
Adrian Klaver
adrian.klaver@aklaver.com