A compromise that works well is to get the DBA to change the
CURSOR_SHARING instance parameter from EXACT to FORCE. This pretty
much simulates the effects of using bind variables without having to
do changes to the application code.
Not quite as efficient as using bind variables, but works well.
"Eugene Staten" <estaten_at_NOSPAMPLZcox.net> wrote in message news:<106kiotevtlem53_at_news.supernews.com>...
> Use prepared statments like Jim explained.
> It would not hurt to place some of your more common queries and inserts into
> Stored Procedures.
>
> SPs help with big queries updates, or inserts.
>
> "Ivan" <ilee_at_bigpond.net.au> wrote in message
> news:90137e1b.0403301523.55aed707_at_posting.google.com...
> > Hi all,
> >
> > I have an application that is written in servlets that connects to an
> > oracle database 8.1.7 via jdbc. My DBA has just notify me that I am
> > not using bind variables in my code and was wondering what i'll need
> > to change to utilise this.
> >
> > At the moment i am just opening a connection, making a statement (sql
> > query) and executing it to return a resultset. Would i need to change
> > all my queries to stored procedures so that bind variables are used or
> > is there another way.
> >
> > thanks all
Received on Fri Apr 02 2004 - 10:40:43 CST
