| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Filling Missing Primary Key Values |
| Date: | 2011-08-11 20:20:25 |
| Message-ID: | alpine.LNX.2.00.1108111317530.14240@salmo.appl-ecosys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 11 Aug 2011, Steve Atkins wrote:
> This will fail if any of the existing values are integers in the range that
> you're inserting - and it may fail in the future, as you add new records
> if they clash with existing entries.
Steve/Chris/Dave:
I had not looked in deatil at that column before. Having just done this, I
see that it's really a laboratory number, not a unique sample ID. So, I
renamed sample_id to lab_nbr, added a sample_id column, created the sequence
sample_id_seq, updated the table with it, then added the constraint that
sample_id is the primary key.
Thank you all very much!
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2011-08-11 21:57:57 | suggestions for archive_command to a remote standby |
| Previous Message | Geoffrey Myers | 2011-08-11 20:12:23 | Re: is max connections in a database table somewhere |