Re: Spring JDBC and the PostgreSQL JDBC driver - Mailing list pgsql-general

From John R Pierce
Subject Re: Spring JDBC and the PostgreSQL JDBC driver
Date
Msg-id 533DD11F.4070705@hogranch.com
Whole thread Raw
In response to Re: Spring JDBC and the PostgreSQL JDBC driver  (Matthew Chambers <mchambers@wetafx.co.nz>)
Responses Re: Spring JDBC and the PostgreSQL JDBC driver  (Matthew Chambers <mchambers@wetafx.co.nz>)
List pgsql-general
On 4/3/2014 1:31 PM, Matthew Chambers wrote:
> This removes all the boilerplate associated with old style JDBC.  It
> also means you get great reuse of your SQL code since the transaction
> starts at the entry point.  Most of my SQL related code is just 1
> liners using Springs JdbcTemplate class.  I've written some massive
> applications with this style.  My current postgres project sees about
> 4gbps of traffic during peak times and there is not an explicit
> begin/commit in the entire code base.

so how does the OP use Jdbc4Array.getArray()  on an object returned from
a Spring execute if Spring has automagically released/closed the connection?



--
john r pierce                                      37N 122W
somewhere on the middle of the left coast



pgsql-general by date:

Previous
From: Matthew Chambers
Date:
Subject: Re: Spring JDBC and the PostgreSQL JDBC driver
Next
From: Merlin Moncure
Date:
Subject: Re: SSD Drives