Re: Spring JDBC and the PostgreSQL JDBC driver

John R Pierce <pierce@xxxxxxxxxxxx> · Thu, 03 Apr 2014 09:39:35 -0700



    On 4/3/2014 9:10 AM, Miller, Michael W
      wrote:

    
      The issue I’m running into is the interaction
        between the Spring Framework JDBC functionality and the
        PostgreSQL JDBC driver. The specific issue is that I’m using
        SimpleJdbcCall.execute() to call the database and getting back a
        Jdbc4Array. When I then try to do something like
        Jdbc4Array.getArray() I get a SQL error that can be tracked down
        to the Jdbc driver trying to use a connection object which has
        already been closed by the Spring Framework.
       
      One of the benefits of the Spring Framework
        is that I don’t have to bother with the drudge work like
        creating\closing connections. The drawback seems to be that the
        JDBC driver is making assumptions like the connection is still
        open.
    
    
    if that framework is opening/closing connections on every query, its
    broken from a performance perspective.   and if it has methods that
    return objects, that are then broken, THATS also broken behavior.

    
    but yeah, this belongs on the jdbc list.

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