| From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
|---|---|
| To: | davidb(at)vectormath(dot)com |
| Cc: | sheila bel <sheilabel(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] using ID as a key |
| Date: | 2000-02-04 22:39:46 |
| Message-ID: | 389B5532.E820BBA9@austin.rr.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
davidb(at)vectormath(dot)com wrote:
>
> Hi Sheila,
>
> For general database design considerations (not specific to Postgres) I
> disagree with the others on the use of serials and sequences. These
> things never migrate well from platform to platform, they often break, and
> dealing with them is a nightmare if you ever have to do any bulk data
> copying.
> ID generation ought to be handled programmatically.
I'm ignorant of these problems with serials, but would like to
consider how to avoid them. Can you give examples of these 3 cases?
Cheers,
Ed Loehr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kaiq | 2000-02-04 22:56:11 | Re: [GENERAL] using ID as a key |
| Previous Message | Hannu Krosing | 2000-02-04 22:37:35 | Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL |