| From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
|---|---|
| To: | Jeff Davis <list-pgsql-hackers(at)empires(dot)org> |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MySQL vs PostgreSQL. |
| Date: | 2002-10-12 02:16:24 |
| Message-ID: | 20021012021624.GB4443@dcc.uchile.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
On Fri, Oct 11, 2002 at 07:08:18PM -0700, Jeff Davis wrote:
> And it really is a minor matter of convenience. I end up dropping and
> recreating all my tables a lot in the early stages of development, which is
> mildly annoying. Certainly not as bad, I suppose, as if you're led to believe
> that a feature does something safely, and it kills all your data.
Now that ALTER TABLE DROP COLUMN is implemented, there probably isn't
any more the need to do such frequent drop/create of tables.
And things just keep getting better and better. This is really amazing.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"We are who we choose to be", sang the goldfinch
when the sun is high (Sandman)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-10-12 04:18:23 | Re: MySQL vs PostgreSQL. |
| Previous Message | Jeff Davis | 2002-10-12 02:08:18 | Re: MySQL vs PostgreSQL. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-10-12 04:18:23 | Re: MySQL vs PostgreSQL. |
| Previous Message | Jeff Davis | 2002-10-12 02:08:18 | Re: MySQL vs PostgreSQL. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2002-10-12 03:31:25 | Re: Out of memory error on huge resultset |
| Previous Message | Jeff Davis | 2002-10-12 02:08:18 | Re: MySQL vs PostgreSQL. |