The code sample worked great for SELECTs. Thanks, Barry.
Is there anything for bunching up a several rows of INSERTs and call a
stored procedure to take care of it instead of requesting an INSERT from the
client-side for every new record?
-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of Barry Lind
Sent: Monday, June 10, 2002 10:39 PM
To: Arthur & Kathy Yeo
Cc: pgsql-jdbc@postgresql.org
Subject: Re: [JDBC] Getting ResultSet using JDBC when calling
Stored-Procedures
Check out http://fts.postgresql.org/db/mw/msg.html?mid=1354157 from the
mail archives.
--Barry
Arthur & Kathy Yeo wrote:
>
> -----Original Message-----
> From: Arthur & Kathy Yeo [mailto:ayeo@acm.org]
> Sent: Monday, June 10, 2002 8:25 PM
> To: pgsql-jdbc@postgresql.org
> Subject: Getting ResultSet using JDBC when calling Stored-Procedures
>
>
> In reading the docs for PL/pgSQL, I noticed that there is no mention about
> PL/SQL-TABLES which in Oracle allows stored procedures to do a SELECT and
> return all the rows thru one of its OUT arguments.
>
> Some people suggested that we can get the stored procedure to return a
> CURSOR and the caller can access that cursor thru JDBC. The only method I
> saw related to cursor in JDBC is getCursorName().
> Anyone know how to access a returned CURSOR coming back from a
> stored-procedure at the JDBC interface?
>
> Similar needs in doing a bulk INSERTs thru a stored procedure.
>
> --
> Arthur
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org