| From: | "Bret S(dot) Lambert" <bret(dot)lambert(at)gmail(dot)com> |
|---|---|
| To: | Andrej <andrej(dot)groups(at)gmail(dot)com> |
| Cc: | Terry <td3201(at)gmail(dot)com>, Andy Colson <andy(at)squeakycode(dot)net>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: data dump help |
| Date: | 2010-01-19 05:40:38 |
| Message-ID: | 20100119054038.GA20214@FlamingKaty.my.domain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 19, 2010 at 06:35:10PM +1300, Andrej wrote:
> 2010/1/19 Bret S. Lambert <bret(dot)lambert(at)gmail(dot)com>:
>
> > Isn't this just over-engineering? Why not let the database do
> > the work, and add the column with a default value of 0, so that
> > you don't have to modify whatever 3rd-party app dumps the data:
>
> But what if his third-party software does something silly like a "select *"
> on the table and then gets a hissy fit because the data doesn't match
> the expectations any longer?
He said his app logs there, so I kind of assumed that it's write-only
as far as the app is concerned. If not, then, yes, there could be
issues.
But why not keep things as simple as possible?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Johan Nel | 2010-01-19 06:06:02 | Re: data dump help |
| Previous Message | Andrej | 2010-01-19 05:35:10 | Re: data dump help |