Comments on: What’s wrong with Hibernate, #1 http://biotext.org.uk/whats-wrong-with-hibernate-1/ Not a typewriter Sat, 07 Jan 2012 11:30:25 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Andrew http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-38 Andrew Sat, 03 Jan 2009 14:51:15 +0000 http://biotext.org.uk/?p=53#comment-38 Brandon, perhaps unit-testing wasn't the right phrase, but I certainly have JUnit tests that bring up the Hibernate session in order to test that it's working as advertised. Fortunate really, since it turned out that it wasn't -- see #2 in this series for one or two examples. Brandon, perhaps unit-testing wasn’t the right phrase, but I certainly have JUnit tests that bring up the Hibernate session in order to test that it’s working as advertised.

Fortunate really, since it turned out that it wasn’t — see #2 in this series for one or two examples.

]]> By: Brandon http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-32 Brandon Sun, 28 Dec 2008 20:05:58 +0000 http://biotext.org.uk/?p=53#comment-32 Unit testing? Why are you hitting the database for your unit tests? You shouldreally be mocking out the Hibernate stuff anyway. Consider it an opportunity to write better unit tests. :-) Brandon Unit testing? Why are you hitting the database for your unit tests? You shouldreally be mocking out the Hibernate stuff anyway. Consider it an opportunity to write better unit tests. :-)

Brandon

]]> By: Mark http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-31 Mark Sun, 28 Dec 2008 19:03:14 +0000 http://biotext.org.uk/?p=53#comment-31 @Dan 1. HQL - what is wrong? 2. use annotations. 3. Really? I am not having problems. 4. Usually because the developer modeled in correctly. 5. So? 6. LOL. too funny. It is an important part but not the center of the app universe. If it is for you, then you have a major architectural issue. @Dan
1. HQL – what is wrong?
2. use annotations.
3. Really? I am not having problems.
4. Usually because the developer modeled in correctly.
5. So?
6. LOL. too funny. It is an important part but not the center of the app universe. If it is for you, then you have a major architectural issue.

]]> By: Dan Howard http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-28 Dan Howard Sun, 28 Dec 2008 15:31:24 +0000 http://biotext.org.uk/?p=53#comment-28 Only one? There are many problems with Hibernate. 1 HQL 2 XML 3 Lousy generic support 4 Lousy Performance 5 Huge distro 6 Hides the database which is the most important part of an app. etc. etc. Only one? There are many problems with Hibernate.

1 HQL
2 XML
3 Lousy generic support
4 Lousy Performance
5 Huge distro
6 Hides the database which is the most important part of an app.
etc.
etc.

]]> By: angel.pinazo@tresese.es http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-19 angel.pinazo@tresese.es Sat, 27 Dec 2008 13:40:29 +0000 http://biotext.org.uk/?p=53#comment-19 I've been using Hibernate for several years and I really like it. But with the coming of EJB3 and other company's JPA implementations, I think it could be abandoned in two or three years. Angel Pinazo Smart Soft Solutions www.tresese.es I’ve been using Hibernate for several years and I really like it. But with the coming of EJB3 and other company’s JPA implementations, I think it could be abandoned in two or three years.

Angel Pinazo
Smart Soft Solutions
http://www.tresese.es

]]> By: Andrew http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-16 Andrew Sat, 27 Dec 2008 12:39:04 +0000 http://biotext.org.uk/?p=53#comment-16 Thanks for the tips regarding the error log. I'll look into this when I'm back at my office. Perhaps I've been spoilt by using Guice a lot recently, which goes out of its way to tell you where you screwed up, and how, and often how to fix it. But -- do you still get the error log details when you get an NPE from the HQL parser, as mentioned in the next rant and here: http://forum.hibernate.org/viewtopic.php?p=2401637 I'm sceptical to be honest, but I'll test it and see. Regarding the fail-fast or fail-on-use question, I guess this is a subjective issue, but from a unit-testing POV it feels a little bit weird seeing completely unrelated tests fail. Thanks for the tips regarding the error log. I’ll look into this when I’m back at my office. Perhaps I’ve been spoilt by using Guice a lot recently, which goes out of its way to tell you where you screwed up, and how, and often how to fix it.

But — do you still get the error log details when you get an NPE from the HQL parser, as mentioned in the next rant and here:

http://forum.hibernate.org/viewtopic.php?p=2401637

I’m sceptical to be honest, but I’ll test it and see.

Regarding the fail-fast or fail-on-use question, I guess this is a subjective issue, but from a unit-testing POV it feels a little bit weird seeing completely unrelated tests fail.

]]> By: Gavin http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-14 Gavin Sat, 27 Dec 2008 12:20:39 +0000 http://biotext.org.uk/?p=53#comment-14 Sounds like *you* swallowed the stack trace, or perhaps did not look far enough down it. I'm sure you'll find the underlying error a bit further down the stack trace. FYI, exception wrapping is a *good* practice, not a bad practice. Sounds like *you* swallowed the stack trace, or perhaps did not look far enough down it. I’m sure you’ll find the underlying error a bit further down the stack trace. FYI, exception wrapping is a *good* practice, not a bad practice.

]]> By: Max http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-9 Max Sat, 27 Dec 2008 08:24:11 +0000 http://biotext.org.uk/?p=53#comment-9 The log will have the details since there can be multiple errors which is not easily captured in a stacktrace. The log will have the details since there can be multiple errors which is not easily captured in a stacktrace.

]]> By: Marcos Silva Pereira http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-8 Marcos Silva Pereira Fri, 26 Dec 2008 21:48:13 +0000 http://biotext.org.uk/?p=53#comment-8 Maybe Hibernate must provide a configuration to enable/disable checking named queries on initialization. But, actually, I really like this feature (because I get the errors sooner). Kind Regards Maybe Hibernate must provide a configuration to enable/disable checking named queries on initialization. But, actually, I really like this feature (because I get the errors sooner).

Kind Regards

]]> By: stanasic http://biotext.org.uk/whats-wrong-with-hibernate-1/comment-page-1/#comment-4 stanasic Fri, 26 Dec 2008 20:20:56 +0000 http://biotext.org.uk/?p=53#comment-4 Andrew, I stumbled across your blog via DZone. From the title of the post(s), I expected something more serious. All your rants, however, seem to be a product of you being too quick to code before reading the documentation. Hibernate will produce the output of what is wrong with query in its ERROR log. Parsing errors will include the character number where the error occurred. Along with the exception itself, it is always enough to pinpoint the problem. Somewhat of an issue here, though, is that when using @NamedQuery annotation, entire text of query will be concatenated into one line; making it more difficult to spot the problematic place. Still, it is very easy to setup a Hibernate Console plug-in in Eclipse, and test all queries interactively, before writing them in your code. > An error in a query will often cause all your tests to fail. Not just ones that use that query. I don't see a problem here. All tests fail because SessionFactory can't be built for each one of them - because named queries are evaluated during configuration. What kind of behavior would you expect? Isn't it better for Hibernate to fail-fast in this situation, since you surely won't be deploying queries with errors in production, would you? Andrew, I stumbled across your blog via DZone. From the title of the post(s), I expected something more serious. All your rants, however, seem to be a product of you being too quick to code before reading the documentation.

Hibernate will produce the output of what is wrong with query in its ERROR log. Parsing errors will include the character number where the error occurred. Along with the exception itself, it is always enough to pinpoint the problem.

Somewhat of an issue here, though, is that when using @NamedQuery annotation, entire text of query will be concatenated into one line; making it more difficult to spot the problematic place.

Still, it is very easy to setup a Hibernate Console plug-in in Eclipse, and test all queries interactively, before writing them in your code.

> An error in a query will often cause all your tests to fail. Not just ones that use that query.

I don’t see a problem here. All tests fail because SessionFactory can’t be built for each one of them – because named queries are evaluated during configuration. What kind of behavior would you expect? Isn’t it better for Hibernate to fail-fast in this situation, since you surely won’t be deploying queries with errors in production, would you?

]]>