| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Stuart McGraw <smcg2297(at)frii(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: changing multiple pk's in one update |
| Date: | 2009-04-13 17:02:31 |
| Message-ID: | 396486430904131002p3faa978fn69bab2872a017436@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, Apr 10, 2009 at 11:20 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stuart McGraw | 2009-04-13 17:20:01 | Re: changing multiple pk's in one update |
| Previous Message | Stuart McGraw | 2009-04-13 16:53:47 | Re: changing multiple pk's in one update |