From: | Bob Pawley <rjpawley(at)shaw(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Ragnar <gnari(at)hive(dot)is>, Postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: serial column |
Date: | 2006-09-25 02:03:29 |
Message-ID: | 010601c6e046$cc0a08a0$8e904618@owner |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The numbering system is more complex than just assigning a number. It
invloves about thirty procedures which I have put together and find that it
works well.
I would like to keep the numbering as a database system which will be
possible if I can figure out a way of generating sequential numbers without
possibility of a gap.
Perhaps a manually built table is the answer??
Bob
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bob Pawley" <rjpawley(at)shaw(dot)ca>
Cc: "Ragnar" <gnari(at)hive(dot)is>; "Postgresql" <pgsql-general(at)postgresql(dot)org>
Sent: Sunday, September 24, 2006 4:30 PM
Subject: Re: [GENERAL] serial column
> Bob Pawley <rjpawley(at)shaw(dot)ca> writes:
>> I am using the numbers to identify devices.
>> If a device is deleted or replaced with another type of device I want the
>> numbering to still be sequential.
>
> It sounds to me like you oughtn't be storing these numbers in the
> database at all. You just want to attach them at display time --- they
> are certainly utterly meaningless as keys if they can change at any
> moment.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2006-09-25 02:10:34 | Re: Restart after poweroutage |
Previous Message | timasmith | 2006-09-25 01:45:12 | postgresql ddl scripts - drop object fails entire script |