pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Broersma <richard.broersma@gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Stuart McGraw <smcg2297@frii.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: changing multiple pk's in one update
Date: Mon, 13 Apr 2009 10:02:31 -0700
Message-ID: <396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com> (raw)
In-Reply-To: <dcc563d10904101120y49f00977nc74132e982518444@mail.gmail.com>
References: <49DC1034.1060705@frii.com>
	<dcc563d10904101120y49f00977nc74132e982518444@mail.gmail.com>

On Fri, Apr 10, 2009 at 11:20 AM, Scott Marlowe <scott.marlowe@gmail.com> wrote:

> Generally speaking, when you need to do this more than once or twice
> in the lifetime of your data, there's something wrong with your data
> model.

True, but there are a few non-traditional data models that would
benefit from this feature.   The two that come to my mind are the
Celko nested set tree model, and sequenced temporal tables.


-- 
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug



view thread (15+ messages)  latest in thread

Message-ID: <396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com>
Permalink:  ../396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com/
Also on:    postgresql.org/message-id/396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: richard.broersma@gmail.com, scott.marlowe@gmail.com, smcg2297@frii.com
  Subject: Re: changing multiple pk's in one update
  In-Reply-To: <396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox