Re: Multiplicity, Change and MV
Date: Tue, 11 Apr 2006 11:18:19 +0300
Message-ID: <e1fonk$lak$1_at_emma.aioe.org>
"dawn" <dawnwolthuis_at_gmail.com> wrote in message news:1144721781.129744.123080_at_v46g2000cwv.googlegroups.com...
> JOG wrote:
> <snip>
> > In the area I work in, changes in cardinality and table schema are
> > rife. Scientific data, especially the way we want to contextualize and
> > record it, is changing constantly (this is one of the reasons that the
> > hideous EAV model got so much funding). Perhaps I just have to accept
> > structural and hence query change via the RM, but perhaps there is a
> > solution that will suit my theoretic demands as well as being
> > practically effective?
> I would guess that using products I have little experience with such as
> Berkeley-DB and Cache' or products I have more experience with such as
> plain-old indexed sequential files (e.g. VSAM), Pick, and maybe even
> IMS could all typically yield more effective, efficient, and less
> expensive solutions for the long haul than the average SQL-DBMS
> solution.
If you are a really good programmer as all of us are :-) then you are right,
an assembler would suffice.
One can do wonderful things with assembler like writing viru ..a a a
software agents . :-)
Received on Tue Apr 11 2006 - 10:18:19 CEST