Petar
Wed Jan 24 03:15:58 CST 2007
orenl wrote:
> for example every DataTable inherits from MyDataTable :
> will have a primaryKey named Id.
> may implement a service that apply persistance
> (where unlike interface, with a abstract DataTable I can create a
> default behavior which is generally sufficient).
>
> Im building a new framework based on DataSet and there are many more
> features that come up on the way and I can only apply them by an
> abstract DataSet.
> keep in mind that I do not want to give up the use in the VS designer
> so Iam in a bit of a problem.
>
1) I have developed a framework based on DataSets and should warn you
that this maybe is not such a good idea. For example say you want to
publish your business entity (dataset) on web service. Nobody except
.NET app could use it. For example look at:
http://www.hanselman.com/blog/ReturningDataSetsFromWebServicesIsTheSpawnOfSatanAndRepresentsAllThatIsTrulyEvilInTheWorld.aspx
2) Maybe you should consider a situation when you must develop an app
that works on some existing database and you find that in that database
you have a table that has an primary key that is of string type.
3) DataSet is meant to be an data structure that is not aware of source
of data. You could get data in dataset from XML, database, flat file,
... So persistance service should not be implemented in MyDataTable.
Regards
Petar Repac