| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | SCassidy(at)overlandstorage(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org>, Steven Brown <swbrown(at)ucsd(dot)edu> |
| Subject: | Re: Changing ids conflicting with serial values? |
| Date: | 2005-11-03 17:46:47 |
| Message-ID: | 1131040006.4892.11.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
[snip]
On Thu, 2005-11-03 at 18:02, SCassidy(at)overlandstorage(dot)com wrote:
> Strange - I had never realized that PostgreSQL would allow you to UPDATE a
> primary key value. I thought that other db's I had used (e.g. Sybase,
> Oracle, SQL Server, etc.) in the past would not allow that, and you had to
> DELETE, then INSERT to modify a row that needed a different primary key.
Well, you're wrong about that too... Oracle at least will definitely let
you update a primary key. The primary key is technically nothing more
than a unique, not null restriction, plus an index on it, otherwise you
can do with it what you wish.
> [snip]
Cheers,
Csaba.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard_D_Levine | 2005-11-03 17:58:06 | Re: OT It is here: Oracle 10g Express |
| Previous Message | Bricklen Anderson | 2005-11-03 17:25:27 | Re: how to emit line number in a function? |