It doesn't deal with the Object->Relational mapping at all. It does the Relational to Object mapping. The real trick here is that the DataSet can hold the data as relational and display hierarchically. I repeat this does *NOT* work to map your objects to a datastore, only the other way around.
It is really just a very convinient way to avoid writing business logic layers that I have had to write for years. Thanks, Shawn Wildermuth [EMAIL PROTECTED] > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]] > On Behalf Of Peter Foreman > Sent: Friday, May 10, 2002 3:42 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] OT: Relational to Object mapping. > > > This depends very much on what design pattern you are using > for OR mapping. Martin Fowler's site [1] gives a good > overview of some approaches. > > What is your approach to inheritance hierarchies for > instance? How does it work if the database schema already > exists and tables do not map 1-1 with objects? > > Peter Foreman > > [1] www.martinfowler.com > > --- Shawn Wildermuth <[EMAIL PROTECTED]> wrote: > > On another note, as soon as I finishing shipping my > manuscript to the > > publisher, I am going to get back to work on my DBFormatter > that would > > allow you to serialize directly to a database. It is not > as easy as I > > first thought, but I think it will worked. This was my preferred > > methodology, but on the other hand, Relation->Object > mapping (not the > > otherway around) is supported really well by DataSets > (IMHO). Since > > you can derive from DataSet (or Typed DataSet) using the DataSet as > > the basis for your business object layer is fairly trivial. > > > > Thanks, > > > > Shawn Wildermuth > > [EMAIL PROTECTED] > > > > > -----Original Message----- > > > From: dotnet discussion [mailto:[EMAIL PROTECTED]] > > > On Behalf Of Jim Arnold > > > Sent: Friday, May 10, 2002 11:31 AM > > > To: [EMAIL PROTECTED] > > > Subject: Re: [DOTNET] OT: Relational to Object mapping. > > > > > > > > > I've spent the last 9 months or so making (or attempting to > > > make) a persistence tier - along the lines of a PersistentObject > > > inheritance pattern, so I might have something to add. .Net > > > desperately needs a proper O/R mapping tool or object > database, and > > > a community project would be a great idea. > > > > > > I was actually eagerly awaiting Thomas' product - it would be a > > > shame if it didn't see the light of day. > > > > > > Jim > > > > > > > -----Original Message----- > > > > From: Murphy, James [mailto:[EMAIL PROTECTED]] > > > > Sent: 10 May 2002 16:25 > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: [DOTNET] OT: Relational to Object mapping. > > > > > > > > *** It might. I have an O/R mapper here ready for about > > > half a year > > > > > - it was supposed to become a product but will probably never. > > > > We seriously > > > > > think of making it open source :-) > > > > > > > > Perhaps when you if there is enough interest (and I'm further > > > > along) we > > > > could get something going here. > > > > > > > > Jim > > > > > > You can read messages from the DOTNET archive, unsubscribe from > > > DOTNET, or subscribe to other DevelopMentor lists at > > > http://discuss.develop.com. > > > > > > > You can read messages from the DOTNET archive, unsubscribe from > > DOTNET, or subscribe to other DevelopMentor lists at > > http://discuss.develop.com. > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
