I'm sitting in a design meeting with a bunch of frigtard Java developers and they're beginning to piss me off. They're talking about using Hibernate to connect to my beloved Oracle database. All these friggin O/R mapping frameworks generating these inefficient SQL queries just gives me the twitches. These guys don't know what the hell they are talking about! One day it's this, the next day it's that. I couldn't wait for those frigtards to stop yapping so I cold-cocked the one sitting next to me to get their attention and said, "GAVIN SUCKS! HIBERNATE SUCKS! WE ARE DOING EVERYTHING WITH STORED PROCEDURES!"
Peace out...
About Me
- Fake Jeff
- I play drums. I fly planes. I fix databases. Developers upset me.
14 comments:
If those frigtard developers really know what they were doing they would run all of their Java code inside the Oracle Database. That would make it at least palatable.
Jeff,
I am linux/python developer.
I totally agree with you. Hibernate is a piece of junk. Of course the logic (stored procedures) has to reside in the database and not in some silly middle-tier layer in which nobody knows what the hell is going on. Them java developers just don't want to use anything else than java. Probably because of the limited brain size of them javamen.
Hans
Hibernate does suck. Here's my theory why people use it: because if they just use the database directly then they are lowering themselves technically to being "database application developers" but if they stick a layer in between then they can remain sun gods who are developing key applications and not soiling their hands on the database. It's all about ego and the techno b.s. is hard to fight. Keep on fighting, may the simplest app win.
I Agree! I think Hibernate sucks. I have 15+ years of database experience using a combo of Oracle, DB2, MySQL, 8 years J2EE, lots of open source expierence, and a Masters degree in Software Engineering from a very well known university in Chicago. I thought Hibernate ORM would relieve some of the grunt work of JDBC, thats why I chose it. I'm sorry I did, should have went with Ibatis. Posted some design questions on Hibernate forum and got no replies. Thats cause there is no way to do what I wanted to do. I have to jump thru hoops to do routine stuff using Hibernate. Just can't see any advantage of using it at all. I can get my work done in a fraction of the time without using Hibernate.
Yeah Jeff, you are right. Hibernate really sucks!!!
What a piece of CRAP Hibernate is! I can't even do a simple select distinct between a date range! It duplicates the result set returned. Distinct only works if I leave off the fromDate.
select distinct someprefix.myDate from my_table someprefix where someprefix.myDate >= ? and someprefix.myDate <= ? order by someprefix.myDate desc
I'm having trouble finding time to reengineer all I've done in Ibatis. I'm the only application developer on the project and I'm sorry I chose this pathetic piece of crap to work with. In the mean time, user requests are pouring in ...
Hmmmm. OK. Hibernate may not be the best tool for generating queries against the database. They're not very efficient queries, but it does seem like Hibernate might be a good solution that bridges the line of easily generating code to get data from a database while still allowing for a good line of testing of the code.
Methinks that doing everything in stored procedures follows more into the area of all-around generally bad ideas. It puts more work on the database rather than in a more logical middle tier that is highly more scalable. It also put business logic in a place that is harder to provide a good suite of testing.
Hibernate is the single worst piece of pointless fuck-ware I have ever used. It is the solution to a problem that doesn't exist. Just thinking about hibernate fills me with tension and hatred. Damn....I REALLY hate hibernate...
That's true because: Relational > Object
Hibernate sucks, its true. But oracle is a way worse technology stuck in the time..just like you!
Totally agree - Hibernate SUCKS INCREDIBLY:
I am experienced Java developer who likes keep things simple and designed complex (> 50 entities with complex relationships and > 1 million rows in some tables) productions level system. I used pure JDBC invoking plain SQL + stored procedures written by database experts which managed to retrieve thousands of entities (yeah also with one-to-many relationships) in no time. When I look back 2 years from now I thank God & my mind I didn't stick to Hibernate then (luckily I had experience with it as Junior developer) - Hibernate uses plenty of reflection, boxing and yeah - SUPER UGLY HQL which can only do plain selects from one or two tables - if one needs something more complex - get ready for some serious problems, numerous stupid selects.
Sorry for hate speech, but I've just switched to another project using Hibernate and it sucks SOOOO MUCH - I constantly need to drop down to plain SQL to do simplest things.
BEWARE JAVA ARCHITECTS - USE PLAIN SQL AND JDBC + libraries like Apache DBUTILS or Spring JDBC Template
Post a Comment