| From: | "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at> |
|---|---|
| To: | "YourSoft *EXTERN*" <yoursoft(at)freemail(dot)hu>, <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC driver bug? |
| Date: | 2007-03-05 14:35:41 |
| Message-ID: | AFCCBB403D7E7A4581E48F20AF3E5DB2018920A9@EXADV1.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> I found the following bug??:
> When you call a pgsql stored procedure (with PreparedStatement), that
> calls an other stored procedure, and you recall the stored procedure
> after dropping and recreating second stored procedure, the calling
will
> throw an exception with:
>
> org.postgresql.util.PSQLException: ERROR: function with OID 63315074
does not exist
Actually, that's a feature, and it has nothing to do with JDBC.
Static SQL in PL/pgSQL ist parsed when you first execute the
function, and the execution plan is retained and used in subsequent
invocations.
If you want a function to use a database object that is dropped and
recreated with the same name, you should use dynamic SQL.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Danny Schueler | 2007-03-05 15:44:26 | jdbc integer value oid to big! |
| Previous Message | Dave Cramer | 2007-03-05 14:28:31 | Re: Switching from MySQL to PostgreSQL, JDBC drivers behaving differently |