From: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
---|---|
To: | Ciprian Popovici <ciprian(at)zuavra(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multi row sequence? |
Date: | 2004-12-19 21:27:22 |
Message-ID: | 1103491642.1867.12.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, 2004-12-19 at 22:43 +0200, Ciprian Popovici wrote:
> On Sun, 19 Dec 2004 13:51:39 +0000 Ragnar Hafstað <gnari(at)simnet(dot)is> wrote:
> > On Sun, 2004-12-19 at 15:02 +0200, Ciprian Popovici wrote:
> > > On Sat, 18 Dec 2004 11:07:37 -0600 Bruno Wolff III <bruno(at)wolff(dot)to>
> wrote:
> > > > On Fri, Dec 17, 2004 at 11:10:12 -0000,
> > > > Filip Wuytack <fwuytack(at)fgscapital(dot)com> wrote:
[question about mysql's special AUTO_INCREMENT on a secondary column in
a multiple-column index]
> > >
> > > Here's a case where what he said would come in handy: arranging a
> > > particular display order within the individual groups. You have the
> unique
> > > key for the entire table, but you need something like a serial
> restricted
> > > to just a group of rows.
> >
> > would a normal sequence not do if that was the only purpose?
>
> Not if you need the main key values to stay put.
I am afraid I do not follow you.
gnari
From | Date | Subject | |
---|---|---|---|
Next Message | Vincent Hikida | 2004-12-20 02:55:01 | Re: UNION with more restrictive DISTINCT |
Previous Message | Ciprian Popovici | 2004-12-19 20:43:14 | Re: Multi row sequence? |