typed dataset

[Guest]

Hi,
We are implementing Data Transfer Objects (DTO) as Typed DataSets. This
means that we would have multiple typed DataSet classes that overlap
slightly, sharing tables between them.
The issue with typed datasets is that it inherits from the DataSet class and
hence a typed dataset class cannot inherit from any other class.
For example consider two datasets MemberDS and AgentDS both sharing a Person
table between them. By default each generated dataset would contain a schema
defining the Person table, meaning that if the table changes, you'll have to
change the schema in two different places. Ideally, you need a way to define
each type once; no matter how many times your application uses or extends
that type. That way, when the shared Person table changes, you'll only have
to modify your code in one place.

We are planning to write a tool that will take of the issues mentioned above.
Your help is welcome.
Thanks

 

[David Young]

I saw your question posted yesterday on the adonet board. I know I didn't
respond because I not really sure what your question is. From a practical
stand point, there are several different schools of thought when It comes to
DTO's. I think you'll find that depending on the architects background,
you'll get different answers.

Personally, I have used typed datasets. On my smaller projects, it just
made sense. They were easy to use and even easier to generate.

For larger, more complex projects, I prefer using custom entity objects. I
guess that's because of my Java history. Definately, it get's a little
hairy when you have a lot of objects and then you mix in your custom
collection classes, but It works for me.
As far a transporting my data from the DAO's to my business logic layer/
business objects, I personally like to use hashtables.