N
Nico
I have some experience in ADO.NET and none in JDO. The articles on JDO
(Java Data Objects - I think) though, seem to suggest that it is a new and
the 'best yet' attempt at solving the relational-object mismatch. From what
I understand, as developer I would really only work with JDO's and link any
sort of backend datastore (Relational, object database, files, XML files and
database etc) to the JDO and truly code against and object model. The JDO's
handle caching, transactions (or makes it very easy for me to manage),
instantiating new instances while sorting out id's an various optimizations.
I got on this track through an article by Dirk Bartels on DevX 'JDO Brings
DB Programming into 21st Century Despite Controversy'
(http://www.devx.com/devx/editorial/16373)
It all sounds great.
In ADO.NET a still work with tables and relations like in a relational
model.
Strongly typed datasets, and similar commercial attempts such as Deklarit,
is actually just mass code generation on an inherantly relational model, and
in my view a weak solution for a very big problem.
So is ADO.NET Microsoft's answer to JDO ? If not, what is ?
(Java Data Objects - I think) though, seem to suggest that it is a new and
the 'best yet' attempt at solving the relational-object mismatch. From what
I understand, as developer I would really only work with JDO's and link any
sort of backend datastore (Relational, object database, files, XML files and
database etc) to the JDO and truly code against and object model. The JDO's
handle caching, transactions (or makes it very easy for me to manage),
instantiating new instances while sorting out id's an various optimizations.
I got on this track through an article by Dirk Bartels on DevX 'JDO Brings
DB Programming into 21st Century Despite Controversy'
(http://www.devx.com/devx/editorial/16373)
It all sounds great.
In ADO.NET a still work with tables and relations like in a relational
model.
Strongly typed datasets, and similar commercial attempts such as Deklarit,
is actually just mass code generation on an inherantly relational model, and
in my view a weak solution for a very big problem.
So is ADO.NET Microsoft's answer to JDO ? If not, what is ?