Even though you are right that there can be distinct advantages MV vs. Relational. But you surely wouldn't want a Product Category file that holds all the product information in multi-valued fields. Or Order and invoice data as multivalued fields in the customer file. There is obviously a little bit more to mv database design than just parent-child relationships.
On 22/12/2010 19:49, Shawn Hayes wrote: > Why would it need to be application specific? I was just thinking that > architecturally (sometimes) there are advantages to using a non first normal > form databases. If you can read the schema of a fully relational database, > couldn't you "easily" enough re-create the files embedding child elements > into > MV tables? > > This would be a great migration path to utilizing some advantages on MV > applications? > > 'We act as though comfort and luxury were the chief requirements of life, > when > all that we need to make us happy is something to be enthusiastic about.' > > > > > ----- Original Message ---- > From: Kevin King <[email protected]> > To: U2 Users List <[email protected]> > Sent: Wed, December 22, 2010 1:34:40 PM > Subject: Re: [U2] Migration > > I would think the migration would be application specific. That said, it > certainly wouldn't be a difficult thing to write. > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
