| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Adam Rich <adam(dot)r(at)sbcglobal(dot)net> |
| Cc: | Sam Mason <sam(at)samason(dot)me(dot)uk>, vinny <vinny(at)xs4all(dot)nl>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: R: Field's position in Table |
| Date: | 2009-08-24 20:26:19 |
| Message-ID: | 20090824202619.GJ5962@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adam Rich wrote:
> For me, saying all new fields must go at the end of the table is like
> saying all new functions must go at the end of your C source file.
> Not that it makes *any* difference to the end user, or other
> applications using your libraries, but as developers we tend to
> be more organized than the general public.
Just because we don't have it implemented does not make it a bad idea.
I think (and others do as well) it's a good idea to be able to handle
this; it's just that nobody has gotten around to implement it.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-08-24 20:30:13 | Re: R: Field's position in Table |
| Previous Message | Sergey Samokhin | 2009-08-24 20:26:15 | Re: How to simulate crashes of PostgreSQL? |