Professional Hibernate (Programmer to Programmer)
ASIN: 0764576771
Average Customer Review: 1.5, based on 20 reviews.
Customer reviews (5 of 20)
Full of typos, 2008-03-11, Rating: 2.
The source code was obviously not proofread. Beyond that, the book is quite readable.
ZERO STARS. Did this book have an editor?, 2006-02-20, Rating: 1.
Total waste of money. As I started reading it, I started to notice coding mistakes everywhere. I thought I was just misunderstanding the topic but then it became clear that these are really mistakes! It is obvious that the code examples were never compiled and tested! Just incredible. Hibernate isn't an easy topic when first encountered, but even a Struts code example has a glaring error!
Any book with code examples should have zero errors in the code - we have had the technology to compile and test every code example in a text since K&R's C book and the Software Tools books in the late 70s. Typically you'll find maybe one typo or error in the prose per chapter in a decent book. I stopped counting and marking within two hours of reading in this book.
This book should be pulled by the publisher and everyone who bought a copy should be offered a written apology and their money back. My copy went out in the weekly paper recycling - I can't afford the chance that any of my engineers might borrow it from my office. I can't imagine how the authors would have put their names on this, let alone their photographs on the front cover.
I confess that I will probably never buy a book from WROX publishers again.
Any book with code examples should have zero errors in the code - we have had the technology to compile and test every code example in a text since K&R's C book and the Software Tools books in the late 70s. Typically you'll find maybe one typo or error in the prose per chapter in a decent book. I stopped counting and marking within two hours of reading in this book.
This book should be pulled by the publisher and everyone who bought a copy should be offered a written apology and their money back. My copy went out in the weekly paper recycling - I can't afford the chance that any of my engineers might borrow it from my office. I can't imagine how the authors would have put their names on this, let alone their photographs on the front cover.
I confess that I will probably never buy a book from WROX publishers again.
Are you kidding me?, 2005-11-17, Rating: 1.
This book was/is badly written and provides erroneous examples... I can't say that I am an expert in Hibernate(far from it), but I found several mistakes in this book. For anyone who is looking to get familiar with the powers of Hibernate don't look here. PLEASE DO NOT LOOK HERE!
Worst tech manual on Hibernate to date:, 2005-11-09, Rating: 1.
If I were the publisher I'd have this book yanked. What an embarrassment. This book gives a very basic understanding of Hibernate and leaves all of the important details out.
Perfect example: at the bottom page 205
We'll discuss each of the joins in detail....
Chapter ends on page 206. Hardly any information whatsoever on a topic that is key to using a database.
For the love of God please take this joke off the shelves. I've never felt so cheated on a tech book in my life. I want my money back!
Perfect example: at the bottom page 205
We'll discuss each of the joins in detail....
Chapter ends on page 206. Hardly any information whatsoever on a topic that is key to using a database.
For the love of God please take this joke off the shelves. I've never felt so cheated on a tech book in my life. I want my money back!
A really bad book - do not buy, 2005-10-19, Rating: 1.
I'm a fan of a lot of Wrox books - I probably own 15-20 of them. This is the wost one I have ever bought.
When learning a new technology with a book, I like to start with an overview, then some simple examples. I read the chapters that cover those start to finish. I then selectively read other parts of the book where I need more detailed knowledge, and save the rest of the book for reference on an as-needed basis. This book was laid out (if you simply look at the Table of Contents) as if I could do that - so I bought it.
The introduction was ok. I've used some object-relational tools before and I wasn't quite sure why Hibernate was special or different. The key thing that it took me WAY too long to figure out was that with Hibernate you're thinking Java-centric and are persisting objects to a database, whereas with other tools you're thinking database-centric and generating a layer of Java objects to access that database. I had to read an awful lot to figure that out.
As others have said, this book is FULL of typos. Among my favorites is the one on page 20 where they introduce the SessionFactory and in the huge diagram they call it "SessionFactor." Glaring and disappointing, but technically it doesn't hinder the learning process (aside from being distracting). On page 28 they give an example where they basically say (paraphrasing) "lets pretend you have a server with an IP address of 192.168.1.55 and a user named 'readwrite'..." they then show the hibernate configuration file right after it and the server's address is 'localhost' and the username is 'sa'. In the following sentence they say to replace localhost with your actual server address, apparently having forgotten all about the 192.168.1.55 address that they started the paragraph with. Awful, and now potentially confusing to people.
Where I really gave up all hope on this book was the first example where they took a program and gave it the ability to persist data with Hibernate. First off, a good demo program should be DEAD simple, so you focus your time reading the code that has to change (Hibernate-related), rather than reading all the code that has to run the demo. Their demo code literally runs from page 33-38, and uses a Swing UI. 5 pages of code for the example, only a small fraction of which the reader should really be focusing on. Now the WORST part. They say that they're going to take this program and step through how to make it persist ("That is the goal of the remainder of this section" they say). The problem is - the example code *already has* all of the hibernate code in it. They go on to step through how to take an example and make it work for hibernate, but never showed you the code BEFORE hibernate was in it.
At this point, after a little more browsing around, I gave up on this book. I should have read the Amazon reviews first. Do yourself a favor and buy a different book based on what the other reviewers have read - that's what I'm going to do.
When learning a new technology with a book, I like to start with an overview, then some simple examples. I read the chapters that cover those start to finish. I then selectively read other parts of the book where I need more detailed knowledge, and save the rest of the book for reference on an as-needed basis. This book was laid out (if you simply look at the Table of Contents) as if I could do that - so I bought it.
The introduction was ok. I've used some object-relational tools before and I wasn't quite sure why Hibernate was special or different. The key thing that it took me WAY too long to figure out was that with Hibernate you're thinking Java-centric and are persisting objects to a database, whereas with other tools you're thinking database-centric and generating a layer of Java objects to access that database. I had to read an awful lot to figure that out.
As others have said, this book is FULL of typos. Among my favorites is the one on page 20 where they introduce the SessionFactory and in the huge diagram they call it "SessionFactor." Glaring and disappointing, but technically it doesn't hinder the learning process (aside from being distracting). On page 28 they give an example where they basically say (paraphrasing) "lets pretend you have a server with an IP address of 192.168.1.55 and a user named 'readwrite'..." they then show the hibernate configuration file right after it and the server's address is 'localhost' and the username is 'sa'. In the following sentence they say to replace localhost with your actual server address, apparently having forgotten all about the 192.168.1.55 address that they started the paragraph with. Awful, and now potentially confusing to people.
Where I really gave up all hope on this book was the first example where they took a program and gave it the ability to persist data with Hibernate. First off, a good demo program should be DEAD simple, so you focus your time reading the code that has to change (Hibernate-related), rather than reading all the code that has to run the demo. Their demo code literally runs from page 33-38, and uses a Swing UI. 5 pages of code for the example, only a small fraction of which the reader should really be focusing on. Now the WORST part. They say that they're going to take this program and step through how to make it persist ("That is the goal of the remainder of this section" they say). The problem is - the example code *already has* all of the hibernate code in it. They go on to step through how to take an example and make it work for hibernate, but never showed you the code BEFORE hibernate was in it.
At this point, after a little more browsing around, I gave up on this book. I should have read the Amazon reviews first. Do yourself a favor and buy a different book based on what the other reviewers have read - that's what I'm going to do.
Projects