Re: [GENERAL] Check constraints and function volatility categories

2016-02-02 Thread Dane Foster
On Mon, Feb 1, 2016 at 4:48 PM, Adrian Klaver wrote: > > >> As an example of where this leads see: >> >> >> http://www.postgresql.org/message-id/7224.1452275...@sss.pgh.pa.us >> >> ​Thanks for the heads up. The good news is all machine access to >> the >> data will be

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Adrian Klaver
On 02/01/2016 01:23 PM, David G. Johnston wrote: On Mon, Feb 1, 2016 at 2:11 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>>wrote: On 02/01/2016 12:52 PM, Dane Foster wrote: On Mon, Feb 1, 2016 at 3:41 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread David G. Johnston
On Mon, Feb 1, 2016 at 2:11 PM, Adrian Klaver wrote: > On 02/01/2016 12:52 PM, Dane Foster wrote: > >> On Mon, Feb 1, 2016 at 3:41 PM, Adrian Klaver > > wrote: >> >> > >> As an example of where this leads see: >> >> http://www.postgresql.org/message-id/72

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Adrian Klaver
On 02/01/2016 12:52 PM, Dane Foster wrote: On Mon, Feb 1, 2016 at 3:41 PM, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote: As an example of where this leads see: http://www.postgresql.org/message-id/7224.1452275...@sss.pgh.pa.us ​Thanks for the heads up. The good news is al

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
On Mon, Feb 1, 2016 at 3:41 PM, Adrian Klaver wrote: > On 02/01/2016 12:36 PM, David G. Johnston wrote: > >> On Mon, Feb 1, 2016 at 1:30 PM, Dane Foster > >wrote: >> >> >> On Mon, Feb 1, 2016 at 2:56 PM, David G. Johnston >> mailto:david.g.johns...@gmail.com>>

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Karsten Hilbert
On Mon, Feb 01, 2016 at 12:41:30PM -0800, Adrian Klaver wrote: >> While you've managed to fool the system by wrapping your query into a >> function you've violated the documented restrictions and so any breakage >> is on you - not the system. > > As an example of where this leads see: > > http:/

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
On Mon, Feb 1, 2016 at 3:36 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Mon, Feb 1, 2016 at 1:30 PM, Dane Foster wrote: > >> >> On Mon, Feb 1, 2016 at 2:56 PM, David G. Johnston < >> david.g.johns...@gmail.com> wrote: >> >>> On Mon, Feb 1, 2016 at 12:41 PM, Adrian Klaver < >>>

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Adrian Klaver
On 02/01/2016 12:36 PM, David G. Johnston wrote: On Mon, Feb 1, 2016 at 1:30 PM, Dane Foster mailto:studdu...@gmail.com>>wrote: On Mon, Feb 1, 2016 at 2:56 PM, David G. Johnston mailto:david.g.johns...@gmail.com>> wrote: On Mon, Feb 1, 2016 at 12:41 PM, Adrian Klaver ma

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread David G. Johnston
On Mon, Feb 1, 2016 at 1:30 PM, Dane Foster wrote: > > On Mon, Feb 1, 2016 at 2:56 PM, David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> On Mon, Feb 1, 2016 at 12:41 PM, Adrian Klaver > > wrote: >> >>> On 02/01/2016 11:17 AM, Dane Foster wrote: >>> Hello, I'm discoverin

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
On Mon, Feb 1, 2016 at 3:22 PM, Dane Foster wrote: > > On Mon, Feb 1, 2016 at 2:41 PM, Adrian Klaver > wrote: > >> On 02/01/2016 11:17 AM, Dane Foster wrote: >> >>> Hello, >>> >>> I'm discovering that I need to write quite a few functions for use >>> strictly w/ check constraints and I'm wonderi

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
On Mon, Feb 1, 2016 at 2:56 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Mon, Feb 1, 2016 at 12:41 PM, Adrian Klaver > wrote: > >> On 02/01/2016 11:17 AM, Dane Foster wrote: >> >>> Hello, >>> >>> I'm discovering that I need to write quite a few functions for use >>> strictly w/

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
On Mon, Feb 1, 2016 at 2:41 PM, Adrian Klaver wrote: > On 02/01/2016 11:17 AM, Dane Foster wrote: > >> Hello, >> >> I'm discovering that I need to write quite a few functions for use >> strictly w/ check constraints and I'm wondering if declaring the >> volatility category for said functions will

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread David G. Johnston
On Mon, Feb 1, 2016 at 12:41 PM, Adrian Klaver wrote: > On 02/01/2016 11:17 AM, Dane Foster wrote: > >> Hello, >> >> I'm discovering that I need to write quite a few functions for use >> strictly w/ check constraints and I'm wondering if declaring the >> volatility category for said functions wil

Re: [GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Adrian Klaver
On 02/01/2016 11:17 AM, Dane Foster wrote: Hello, I'm discovering that I need to write quite a few functions for use strictly w/ check constraints and I'm wondering if declaring the volatility category for said functions will affect their behavior when invoked by PostgreSQL's check constraint me

[GENERAL] Check constraints and function volatility categories

2016-02-01 Thread Dane Foster
Hello, I'm discovering that I need to write quite a few functions for use strictly w/ check constraints and I'm wondering if declaring the volatility category for said functions will affect their behavior when invoked by PostgreSQL's check constraint mechanism. Essentially what I'm trying to figu