I'm not a DBA, however I will protest that I've spent enough time in the trenches to have seen both sides. To me the appeal is a more object orient abstracted view of the data. I'll also admit that it is a far from perfect solution. As a developer I find myself spending hours debugging simple problems due to misconfiguration of Hibernate. I also find performance problems often, and the configuration sometimes struggles with more complicated queries. From a dba view point I hate that adding foreign keys will destroy any functionality (at least with Activerecord/NHibernate in C#) I've used Linq->Sql which is a bit better from a configuration (and performance) point of view, but still has many problems. The problem is a perfect solution just doesn't seem to exist at the moment.
Comments
I'm not a DBA, however I will protest that I've spent enough time in the trenches to have seen both sides. To me the appeal is a more object orient abstracted view of the data. I'll also admit that it is a far from perfect solution. As a developer I find myself spending hours debugging simple problems due to misconfiguration of Hibernate. I also find performance problems often, and the configuration sometimes struggles with more complicated queries. From a dba view point I hate that adding foreign keys will destroy any functionality (at least with Activerecord/NHibernate in C#) I've used Linq->Sql which is a bit better from a configuration (and performance) point of view, but still has many problems. The problem is a perfect solution just doesn't seem to exist at the moment.