| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Elaine Lindelef <eel(at)cognitivity(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Change size of varchar(20) field |
| Date: | 2002-02-05 00:29:46 |
| Message-ID: | 20020205112946.A26418@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 04, 2002 at 11:08:57AM -0800, Elaine Lindelef wrote:
> Has anyone discovered any workaround to the lack of a full ALTER
> TABLE that preserves the OID for each row? I am finding that for
> insurance I have to assign each table an SERIAL of my own to create
> an autoincremented ID that I can control - because using OID as a key
> requires me to update the key throughout the database if I have to
> drop the table.
Probably a good idea anyway since OIDs are not guarenteed to be unique. At
least by using a SERIAL you will notice when the it wraps around. I think in
7.2 the OID column will be optional.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org>
http://svana.org/kleptog/
> Terrorists can only take my life. Only my government can take my freedom.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitch Vincent | 2002-02-05 00:34:20 | Getting fields in a table through a query? |
| Previous Message | Rob Arnold | 2002-02-05 00:14:48 | Re: HASH index method not correctly handling NULL text |