Let me be the first to say that ORM (like Propel) is ridiculous, overengineered nonsense. SQL is already simple. In fact, it was originally designed so that (competent) non-computer people could easily generate reports from a RDBMS. So why does anyone think it’s a good idea to add unnecessary overhead and complexity to something that already works well? Oh yeah, because ORM makes it possible to write your own blog in 15 minutes. Wow. Totally awesome dude.
Latest Tweet
- I'm going to a Meetup with Frontier Developers' Meetup! http://meetup.com/u/1nxW 1 day ago
- More updates...
Posting tweet...
Categories
- /etc (12)
- Apache (3)
- Chef (1)
- DNS (4)
- EC2 (2)
- Ganglia (2)
- Hardware (7)
- Information Technology (7)
- Linux (14)
- MySQL (2)
- Networking (8)
- Programming (26)
- Puppet (1)
- Rants (8)
- Tokyo Tyrant (2)
- Windows (5)
- Wordpress (5)
- Xen (6)
Archives
- July 2010 (2)
- May 2010 (6)
- April 2010 (3)
- December 2009 (1)
- November 2009 (1)
- October 2009 (2)
- September 2009 (6)
- August 2009 (2)
- July 2009 (3)
- June 2009 (3)
- May 2009 (5)
- April 2009 (1)
- March 2009 (1)
- February 2009 (2)
- January 2009 (2)
- December 2008 (4)
- November 2008 (3)
- October 2008 (3)
- September 2008 (1)
- August 2008 (1)
- July 2008 (2)
- June 2008 (2)
- April 2008 (1)
- March 2008 (5)
- February 2008 (3)
- November 2007 (3)
- October 2007 (1)
- September 2007 (1)
- October 2006 (2)
- September 2006 (6)
- August 2006 (2)
- July 2006 (2)
- May 2006 (1)
- April 2006 (3)
- March 2006 (4)
> Propel is really quite simple to use. Basically, you need to define your data model in XML
Yuck.
I know I sound like a Rails fanboy, but you should really check out ActiveRecord. No configuration necessary–it’s all based on your table structure.
But then again, you’d have to switch your entire project to Rails and that’s probably not feasible.
dont mind me. i was just really annoyed after having spent hours trying to get something to work in propel that i could have done in 5 minutes with sql.
Hold the phone.
Hibernate is the best, and I mean THE best persistience layer i’ve ever used. I appreciate Ruby on Rails ActionModels (whatever they’re called) – but I don’t develop ruby that much at the moment.
Hibernate removes a layer of complexity (JDBC) – or at least the dealing with it side of things,and provides an easily resuable, totally abstracted object-relation mapping layer which is absolutely awesome to use in every way, from exception handling, to unit testing, to actual visualisation of your data model instead of a bunch of stupid select statements.
HQL is a bit pointless, but I can see the need for it (db independence anyone?). Its transaction handling is great, and don’t even get me started on query by example! Finally something which removes a level of complexity from J2EE. So required.
I also love spring.