This may not help, but I implemented an attribute like this for DBD::ODBC where someone wanted to create a trigger and the trigger had :new.foo type syntax and DBD::ODBC was doing the exact same thing...If it's plausible, you *might* be able to switch over to DBD::ODBC in the short run for the DDL type statements... Just a thought...
Of course, don't let that discourage you from poking around in the dbdimp code... Regards, Jeff > > On Fri, Oct 25, 2002 at 06:26:29AM +1000, Steve Baldwin wrote: > > Thanks Chris, > > > > I have tried this on DBI 1.30 and DBD::Oracle 1.12, but see > exactly the same > > behaviour. I suspect it is a DBD::Oracle thing coz as far as I > know, named > > bind variables (as opposed to ?) is an Oracle thing. > > > > I have ended up doing the same as you did, but I hate ugly > kludges, and was > > hoping someone could enlighten me with "you just need to set the xxx > > attribute on your database handle and it bypasses bind variable > scanning". > > Not implemented yet, but patched welcome :) > > (I _really_ hope to do some more DBD::Oracle work soon and could > add in such an attribute fairly easily.) > > Tim. > > > If there's no such mechanism already, how about an enhancement > ??? I suppose > > I could get really brave and look in the .xs file, but before I > do that, I > > guess I'd like to hear some confirmation (one way or another) > that that's the > > only other solution. > > > > Thanks for the reply, > > > > Steve > >
