On Tue, Jan 19, 2010 at 06:35:10PM +1300, Andrej wrote:
> 2010/1/19 Bret S. Lambert <bret.lambert@gmail.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?