Re: query manipulation

[Dave Cramer <davec(at)fastcrypt(dot)com>]

Randall,

It would work, but it appears the utility here is to make the  
differences between JDBC versions transparent.

Dave
On 21-Mar-07, at 1:29 PM, Randall Smith wrote:

> Would this be a good tool to use here or would it create  
> unnecessary work?
>
> http://jakarta.apache.org/commons/dbutils/apidocs/org/apache/ 
> commons/dbutils/ProxyFactory.html
>
> public java.sql.PreparedStatement createPreparedStatement 
> (java.lang.reflect.InvocationHandler handler)
>
> Randall
>
>
> Randall Smith wrote:
> > I'm trying to find a way to manipulate some poorly written queries  
> > in which I don't have access to the application source.  I can't  
> > do it at the Postgresql server, so I'm thinking of attacking it at  
> > the jdbc driver.
> > I was thinking of a wrapper that would look at and alter the SQL  
> > before it went to the server.  Anyone know of something like this?  
> > Specifically, I'm trying to drop "FOR UPDATE column name" off of  
> > some queries.  They were written for Oracle, but Postgresql uses  
> > "FOR UPDATE table name".  I'm not a Java programmer, but I won't  
> > let that stop me if it is required.
> > Randall
> > ---------------------------(end of  
> > broadcast)---------------------------
> > TIP 7: You can help support the PostgreSQL project by donating at
> >                http://www.postgresql.org/about/donate
>
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match