Welcome to Hell!
-----Original Message----- From: George Gallen <ggal...@wyanokegroup.com> To: U2 Users List <u2-users@listserver.u2ug.org> Sent: Wed, Nov 9, 2011 10:57 am Subject: Re: [U2] Suggestions for flattening Multivalues... I was looking more for ideas on how to setup the database structure to handle he 1:n other than the Sidebar tables joined to the master table. Right now, the scope of the data being moved off is fairly small, I didn't want o involve any other apps The querying app would be custom in itself (most likely php or something) Just this one file we are moving contains about 20 different multivalued fields, nd it seemed a little verkill to have to create 21 tables to contain the data in a form MySQL can andle. I guess that what appens when you've been raised on multivalue database structure, and are forced o work with one that oes not handle it natively! -----Original Message----- rom: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] n Behalf Of Steve Romanow ent: Wednesday, November 09, 2011 1:41 PM o: U2 Users List ubject: Re: [U2] Suggestions for flattening Multivalues... It might be worth doing some of this work with an ORM (Object Relation apper). Almost all higher level languages have them. Once you get hings configured, the messiness of the joins is hidden behind yntactic sugar. Here is a comparison of a lot of them from wikipedia. ttp://en.wikipedia.org/wiki/Comparison_of_object-relational_mapping_software SQLAlchemy is a market leader for python. If you are a microsoft hop, I understand LINQ us really nice. ttp://en.wikipedia.org/wiki/Language_Integrated_Query#LINQ_to_SQL On Wed, Nov 9, 2011 at 1:34 PM, George Gallen <ggal...@wyanokegroup.com> wrote: I'm in the process of creating/updating a MySQL database for external pplications to analyze some of the data. My initial method of dealing with a multivalued field, is to create it's own able, keyed to the master table (1:n) But this gets a little tedious if you have a bunch of multivalued fields - and reates really bulky SQL statements with all the joins. What other ways are people using to work with 1:n relationships? _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ______________________________________________ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ______________________________________________ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
