Attention: We have retired the ASP.NET Community Blogs. Learn more >

RE: Critique of Disappointing Session at TechEd

I attended a session entitled "Object-Relational Mapping As a Foundation for ADO.NET Database Access" here at TechEd.

 
I did not attend to the presentation, but my boss (yes, Paul, unfortunately it's not 'Andres Aguiar's DeKlarit' ;), attended to it with a friend, and he liked it a lot.
 
For what he told me he discussed some data modeling issues that are difficult to model with a relational database and how to map that to DataSets, That's the kind of thing we do well with DeKlarit and we spend a lot of time thinking about, so that's probably why my boss liked it.
 
He also liked DataSets, as we also do.
 
We are looking forward to talk to him, because his thoughts seemed to be in the same frequency as ours.
 

2 Comments

  • That is funny, because the EntityBroker guys really don't like datasets. I was suprised when they told me that EntityBroker doesn't build on top of DataSets like ObjectSpaces does... that means lots of hand coding for stuff that is already in the framework.

  • The problem, jesse, is that datasets are pretty bad in a number of things. Most namely we dropped them when we got into - inheritance :-) When a list of objects returned from a query may have different fields in every object (polymorphism), datasts get clumsy. Much better to just have an array hidden in every object. All the other stuff (databinding etc.) is useless anyway (we bind at the object level), so it never gets used - so why keep the dataset around?





    THis is something, though, the deklarit people wont notice. Propably because this "gui driven toy" is not able to handle any type of object polymorphism. And if you just manage a dataset and make every table an object type, it is VERY easy to work with datasets. OTOH, I would not call this an O/R mapper - too limited.

Comments have been disabled for this content.