Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!news.glorb.com!news-spur2.glorb.com!homer.glorb.com!.POSTED!not-for-mail From: Steve Sobol Newsgroups: comp.lang.java.programmer Subject: Re: Spring/hibernate and JDBC Date: Sun, 10 Jul 2011 09:42:17 -0700 Organization: Glorb Internet Services, http://www.glorb.com Lines: 18 Message-ID: References: <3c16e5e7-3c0b-4126-9dd9-88f372a58f03@e26g2000prf.googlegroups.com> NNTP-Posting-Host: iPkerGyBvEjTeMef7hbH9w.user.posting2.glorb.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@glorb.com NNTP-Posting-Date: Sun, 10 Jul 2011 16:42:22 +0000 (UTC) User-Agent: MicroPlanet-Gravity/3.0.4 X-Notice: Scanned by Mr. Bill Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6051 In article , Tom Anderson says... > > This has also been my impression. On my current project, we do still write > raw SQL using JDBC on occasion, but only because we need to do some sort > of mad query that can't be done with our persistence provider. I have one of those now, and I just used Hibernate's createSQLQuery() and still get 99% of the advantages of Hibernate/JPA even though I had to create raw SQL. -- Steve Sobol - Programming/WebDev/IT Support sjsobol@JustThe.net