| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Well, then you keep your darn columns |
| Date: | 2000-01-24 16:34:22 |
| Message-ID: | Pine.BSF.4.21.0001241233300.79710-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 24 Jan 2000, Adriaan Joubert wrote:
> As a user let me just say that I have been waiting for all the
> 'ALTER TABLE..' commands for a long time (changing constraints would be great
> too!) and it has been mentioned many times that one should not use oids in
> application code. The way I do it at the moment is to copy the table, so I
> think all users are used to losing their oids when remocing a column from a
> table. So while it is certainly better to keep the oids, Peter's code is a
> big improvement on the current situation.
Except, as Chris Bitmead brought up, OIDs appear to be a key requirement
in ODBMSs ... so, if we want to go what I *think* is 'next generation',
OIDs have to be kept ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-01-24 16:44:25 | Re: [HACKERS] Re: Doc updates for index cost estimator change |
| Previous Message | Bruce Momjian | 2000-01-24 16:29:20 | Re: [HACKERS] column aliases |