On 8/9/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: > A lot of prepared statements are emulated because db apps ( like > mysql ) didn't really support a prepare until recently, and few db > drivers supported an actual server side prepare. DBD::Pg just > emulated it until 1.4 by using internal representations. > > a bunch of dbs work like this with server side prepares > > prepare statement1 from 'SELECT NOW() as time_now' > execute statement1; > deallocate statement1; # removes the satement > > so anyways, getting back to the point.... dbd automagically creates > prepared stuff > > prepare ID from SQL > > where id is just an internal counter on prepares. someone just > submitted a batch to make it prepare PID_ID , to avoid name clashes > under apache::dbi
The DBI API always requires a call to prepare() before execute(), after which it's in the DBD's court. Anything that happens on the DBD side is likely beyond my control unless there are useful options to prepare(). I used to have (undocumented) methods for providing options to most calls to prepare(), but commented this code a while ago because I couldn't think of any useful options to prepare :) -John ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
