Re: Modelling objects with variable number of properties in an RDBMS
Date: Mon, 31 Oct 2005 12:56:04 +0200
Message-ID: <dk4t8a$rha$1_at_domitilla.aioe.org>
"Roy Hann" <specially_at_processed.almost.meat> wrote in message
news:LvGdnZoLb_yebPjeRVnyjA_at_pipex.net...
> "Bernard Peek" <bap_at_shrdlu.com> wrote in message
> news:4tHfgQLCbeZDFw7N_at_shrdlu.com...
> > In message <3fqdnUHV_-Qf__jeRVnyjQ_at_pipex.net>, Roy Hann
> > <specially_at_processed.almost.meat> writes
> > >"Bernard Peek" <bap_at_shrdlu.com> wrote in message
> > >news:9Dc+bybsWUZDFw5n_at_shrdlu.com...
> > >
> > >> That's one reason why people keep trying to use it. The second one,
> > >> unfortunately, is that sometimes it's the only alternative. Sometimes
> > >> you just don't know the whole data structure at design-time.
> > >
> > >One day, ours will be a real profession, and we'll be allowed to say
> "sorry,
> > >you can't do that" without getting fired. In fact we'll have a legal
> duty
> > >to say it, just like engineers and accountants and proper
professionals.
> >
> > But that's not the problem. The problem is that it is possible to build
> > a database using the EAV system, but it will require constant
> > maintenance and skilled users to keep it working.
>
> No that's not the problem. The problem is that it is trivially easy to
> create new tables in an RDBMS--literally in a matter of tens of
seconds--but
> most people seem to think it is both possible and necessary to improve on
> "trivially easy".
> > I wonder whether there's a role for EAV systems in prototyping systems
> > using agile development?
> No, no, no! A thousand times no! What could be more agile than creating
a
> real table? It takes literally seconds.
So a schema of 120 tables can be created in less than 2 hours. The hard part is to make the application. :-) Received on Mon Oct 31 2005 - 11:56:04 CET