Postgres Pro
Downloads
Home   >   mailing lists

Thread: Enforcing CONCUR_*

Enforcing CONCUR_*

From
Oliver Jowett
Date:
I just noticed that CONCUR_READ_ONLY/CONCUR_UPDATEABLE are not enforced
by the driver -- you can update any resultset regardless of the
concurrency setting (assuming it meets the other requirements to be
updateable).

Should we be enforcing that the resultset must be CONCUR_UPDATABLE
before allowing update operations?

-O

Re: Enforcing CONCUR_*

From
Kris Jurka
Date:

On Fri, 28 Jan 2005, Oliver Jowett wrote:

> Should we be enforcing that the resultset must be CONCUR_UPDATABLE
> before allowing update operations?
>

Yes.

Kris Jurka

Re: Enforcing CONCUR_*

From
Oliver Jowett
Date:
Kris Jurka wrote:
> On Fri, 28 Jan 2005, Oliver Jowett wrote:
>
>>Should we be enforcing that the resultset must be CONCUR_UPDATABLE
>>before allowing update operations?
>
> Yes.

Ok, applied to CVS.

-O