Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking
Date
Msg-id 201005300138.o4U1cUC26848@momjian.us
Whole thread Raw
In response to Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking  (David Fetter <david@fetter.org>)
Responses Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking  (David Fetter <david@fetter.org>)
List pgsql-general
David Fetter wrote:
> On Sat, May 29, 2010 at 01:29:50PM -0700, Richard Broersma wrote:
> > This might be a premature question considering write-able CTEs are not
> > in core, but...
> >
> > I wondering if write-able CTE's will be the silver bullet that will
> > make rule based update-able views based multiple vertically
> > partitioned table robust.  By robust, I mean to elimination the
> > update anomalies that can occur from the view point client side
> > optimistic locking where the virtual row appears to be
> > inconsistently updated.
>
> I'm not sure I understand.  When the concurrency issues in writeable
> CTEs get fixed, they could become a mechanism for doing what you
> describe, but I suspect there would be significant work involved in
> harnessing them to that task.
>
> They'll be pretty nice even without the automated view stuff, though :)

If the user wants to submit it, fine, but neither Tom nor I are excited
about it.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

pgsql-general by date:

Previous
From: David Fetter
Date:
Subject: Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking
Next
From: David Fetter
Date:
Subject: Re: Write-able CTEs, Update-able views, Hierarchical data, and optimistic locking