Re: [Info-Ingres] jdbc caches prepared statements?
- From: "Martin Bowes" <martin.bowes@xxxxxxxxxxxxx>
- Date: Wed, 30 Jul 2008 15:54:17 +0100
Hi Kristoff,
I'll check for a fix to that bug number.
Marty
-----Original Message-----
From: info-ingres-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx
[mailto:info-ingres-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
kristoff.picard@xxxxxxxxxx
Sent: 30 July 2008 13:28
To: info-ingres@xxxxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Info-Ingres] jdbc caches prepared statements?
Hi Marty,
the JDBC driver needs to follow the DBMS here.
For the DBMS, in theory I would agree, but it turned out that changing
this behaviour, which was tried years ago, introduced other problems -
so that change was removed.
But back to the JDBC application: When using
PreparedStatement.close(), LATER versions of the driver should remove
this statement from the internal cache (so you have to re-prepare
before executing it again). It also frees the internal statement name,
so if that name is used again to prepare a statement, the old
statement in the DBMS is replaced by the new one(similar to embedded
sql). You need to have the fix for bug 117108 for this. (I haven't
tested this, but this is my understanding)
Kristoff
_______________________________________________
Info-Ingres mailing list
Info-Ingres@xxxxxxxxxxxxxxxxxxxxxxxxx
http://www.kettleriverconsulting.com/mailman/listinfo/info-ingres
.
- References:
- [Info-Ingres] jdbc caches prepared statements?
- From: Martin Bowes
- Re: jdbc caches prepared statements?
- From: kristoff . picard
- Re: [Info-Ingres] jdbc caches prepared statements?
- From: Martin Bowes
- Re: jdbc caches prepared statements?
- From: kristoff . picard
- [Info-Ingres] jdbc caches prepared statements?
- Prev by Date: Re: jdbc caches prepared statements?
- Next by Date: [Info-Ingres] Microsoft buys Datallegro
- Previous by thread: Re: jdbc caches prepared statements?
- Next by thread: Re: [Info-Ingres] get returned value of stored procedure in ingres
- Index(es):
Relevant Pages
|