ORM

[Nishanthan]

Hi,
Any one used any Object relational Mappings(ORM) in your projects? Anyone
have idea of which ORM is better?
Regards,
P.Nishanthan

 

[Jon Skeet [C# MVP]]

Any one used any Object relational Mappings(ORM) in your projects? Anyone
have idea of which ORM is better?

I've used Hibernate in a Java project. There are a few rough edges, but
it's generally great. It's certainly worth at least looking at
NHibernate, although I suspect it's a way behind its "big brother". One
important thing (at least for us - it depends on the nature of your
project) is to look closely at the SQL produced to make sure it's not
pulling in a load of stuff you don't need.

 

[=?ISO-8859-1?Q?Lasse_V=E5gs=E6ther_Karlsen?=]

Hi,
Any one used any Object relational Mappings(ORM) in your projects? Anyone
have idea of which ORM is better?
Regards,
P.Nishanthan

I use DevExpress eXpress Persistent Objects (Xpo) a lot. They have their
limitations but generally they work really good..

 

[Michael S]

Hi,
Any one used any Object relational Mappings(ORM) in your projects? Anyone
have idea of which ORM is better?
Regards,
P.Nishanthan

With .NET3.0 and LINQ I think ORM systems will become obsolete.
However, Hibernate is an excellent framework.

- Michael S

 

[Daniel Jin]

it's not that ORM will be obsolete. everyone will start using DLinq,
Microsoft's ORM solution instead. and other ORM solutions will
continue to exist, they will all support Linq syntax.

 

[Jon Skeet [C# MVP]]

With .NET3.0 and LINQ I think ORM systems will become obsolete.

I assume you mean that *other* ORM systems will become obsolete, as
DLINQ is essentially an ORM system in itself.

I would say that they'll only become obsolete if:
a) .NET 3.0 comes out early enough that people don't have a large stake
in the existing systems.
b) It's actually *better* than the existing systems. This shouldn't be
taken as a given, especially as separate frameworks are likely to be
able to evolve an awful lot quicker than the .NET framework itself.

However, Hibernate is an excellent framework.

Agreed.

 

[Frans Bouma [C# MVP]]

it's not that ORM will be obsolete. everyone will start using DLinq,
Microsoft's ORM solution instead. and other ORM solutions will
continue to exist, they will all support Linq syntax.

I doubt 'everyone' will start using DLinq. For starters, a lot of
developers out there simply believe in tables/raw sql and don't grasp
for whatever reason the object oriented view of a relational model
presented by an O/R mapper.

FB


--