| From: | Stephen Bacon <sbacon(at)13x(dot)com> |
|---|---|
| To: | Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Cc: | Steve Linabery <slinabery(at)worldcycling(dot)com> |
| Subject: | Re: jdbc & tomcat |
| Date: | 2002-08-28 14:49:39 |
| Message-ID: | 1030546180.8881.343.camel@babylon.13x.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Is the drop/recreate being done from a stored procedure? When postgres
compiles a procedure it ends up referencing it by it's OID (Object ID).
When you recreate something it'll get a new OID, and so mess up the
proc.
The workaround is to use EXECUTE in your stored proc so it re-evals the
statement.
I believe the same issue can apply to triggers dependent upon the table.
-Steve
On Wed, 2002-08-28 at 10:14, Steve Linabery wrote:
> someone has some ideas anyway. When I try to access the jsp, the bean's
> Connection throws this exception:
> java.sql.SQLException: ERROR: Relation "dw_adcosts" with OID 597084 no
> longer exists
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anandhi Narayanaswamy | 2002-08-28 15:08:09 | postgreSQL driver installation on Oracle9i Application Server |
| Previous Message | Barry Lind | 2002-08-28 14:31:52 | Re: jdbc & tomcat |