Return-Path: Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 58373 invoked by uid 500); 30 Jul 2003 17:31:05 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 58304 invoked from network); 30 Jul 2003 17:31:03 -0000 Received: from relay.pair.com (209.68.1.20) by daedalus.apache.org with SMTP; 30 Jul 2003 17:31:03 -0000 Received: (qmail 57181 invoked from network); 30 Jul 2003 17:31:04 -0000 Received: from d150.kif4.nas.panafonet.gr (HELO compaq) (213.249.3.150) by relay.pair.com with SMTP; 30 Jul 2003 17:31:04 -0000 X-pair-Authenticated: 213.249.3.150 From: "Cameron Hickey" To: "'Apache Torque Users List'" Subject: RE: Hibernate vs. Torque Date: Wed, 30 Jul 2003 20:32:29 +0300 Message-ID: <000001c356c0$9723ef10$0100a8c0@compaq> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal In-Reply-To: <794AA7B1BE0DB2458F738486D735394318C754@mail.funnygarbage.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Tom, I have been trying to put together a simple data entry interface using Tomcat and Struts, and some data persistance technology. I spent about 3 weeks working with Hibernate, and recently decided to switch and try Torque. Since I have considerable experience developing databases, and much less is java programming, Torque's methodology felt more comfortable and database oriented than Hibernate. Getting it up and running with my application also seemed to be much simpler. I did not use the automatic Class generation tools that Hibernate provides, but they are less well documented than what I saw online for torque. I think that you should certainly give Hibernate a try, because I could easily tell that in terms of robust object persistence, Hibernate definitely has a leg up over Torque due to things like "lazy-initialization" which allows you to intelligently only query the DB for the row(s) you are actually using, instead of more, which can be useful if you have really large tables. The overall documentation of Hibernate is considerable, compared to the palty dozen pages that torque has, but since I managed to get torque working anyway, perhaps that is a testimate to its simplicity. Cameron -----Original Message----- From: Keeney, Thomas [mailto:KeeneyT@SEC.GOV] Sent: Wednesday, July 30, 2003 12:54 PM To: 'torque-user@db.apache.org' Subject: Hibernate vs. Torque Hi all! I've been using Torque for almost 2 years now, and I have to say it's a great product. However, I've been wanting to try another persistence framework lately (call it wanderlust!). Does anyone have any thoughts on using Hibernate and how it compares with Torque? I've checked out the Hibernate documentation and it appears to handle more complex distributed applications better than Torque (optimistic locking support, etc). Thanks, Tom Keeney ------------------------------- Phone: 202-824-5143 --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org