Maybe.  Not yet.

Tim.

On Thu, Nov 21, 2002 at 12:16:41PM -0500, Steven N. Hirsch wrote:
> Cool!
> 
> Is there somewhere I can grab a tarball to beat on prior to release?
> 
> Steve
> 
> 
> On Thu, 21 Nov 2002, Tim Bunce wrote:
> 
> > It's in. I've appended the current change list (but there's more to add yet).
> > 
> > Thanks for the feedback.
> > 
> > Tim.
> > 
> >   The proxy now supports non-lazy (synchronous) prepare, positioned
> >     updates (for selects containing 'for update'), PlRPC config set
> >     via attributes, and accurate propagation of errors, all thanks
> >     to Steven Hirsch (plus a minor fix from Sean McMurray and doc
> >     tweaks from Michael A Chase).
> >   The DBI_AUTOPROXY env var can now hold the full dsn of the proxy driver
> >     plus attributes, like "dbi:Proxy(proxy_foo=>1):host=...".
> >   Added TaintIn & TaintOut attributes to give finer control over
> >     tainting thanks to Bradley Baetz.
> >   The fetchall_arrayref method, when called with a $maxrows parameter,
> >     no longer gives an error if called again after all rows have been
> >     fetched. This simplifies application logic when fetching in batches.
> >     Also added batch-fetch while() loop example to the docs.
> >   The connect() RaiseError/PrintError message now includes the username.
> >   Changed "last handle unknown or destroyed" warning to be a trace message.
> >   Updated dbish/DBI::Shell to Tom Lowery's much improved version.
> >   Updated some minor doc issues thanks to H.Merijn Brand.
> >   Updated Makefile.PL example in DBI::DBD thanks to KAWAI,Takanori.
> >   Documented $dbh = $sth->{Database} attribute.
> >   Documented $dbh->connected(...) post-connection call when subclassing.
> >   Fixed execute_array() example thanks to Peter van Hardenberg.
> >   The CursorName attribute now defaults to undef and not an error.
> >   Removed forced requirement for drivers to implement DESTROY methods.
> >   DBI::Profile changes:
> >     Setup fixes thanks to Sam Tregar.
> >     Added $DBI::err (etc) tied variable lookup time to profile
> >     Added time for DESTROY method into parent handles profile (used to be ignored)
> >  
> >   Changes for driver authors, not required but strongly recommended:
> >     Change DBIS to DBIc_DBISTATE(imp_xxh)   [or imp_dbh, imp_sth etc]
> >     Change DBILOGFP to DBIc_LOGPIO(imp_xxh) [or imp_dbh, imp_sth etc]
> >     Any function from which all instances of DBIS and DBILOGFP are
> >     removed can also have dPERLINTERP removed (a good thing).
> >     All use of the DBIh_EVENT* macros should be removed.
> > 
> > On Thu, Nov 21, 2002 at 07:50:47AM -0500, Steven N. Hirsch wrote:
> > > On Thu, 21 Nov 2002, Tim Bunce wrote:
> > > 
> > > > On Thu, Nov 21, 2002 at 02:07:48AM +1100, Bradley Baetz wrote:
> > > > > Are there plans to have a 1.31 release sometime in the near future? I'd
> > > > > like to move Bugzilla over to using DBI properly, but that needs my
> > > > > Taint patch which was applied a couple of months back. It would be a lot
> > > > > simpler if I could point people to a release rather than having to get
> > > > > them to apply my patch manually.
> > > > 
> > > > Hopefully before the end of next week. Maybe sooner. (Maybe not :)
> > > 
> > > Tim,
> > > 
> > > If a release of 1.31 is truly imminent, can we close on the last suggested 
> > > patch I sent for Proxy?  At the time you were too snowed under to look at 
> > > it, but it's proved to be important.
> > > 
> > > This is the change which localizes the __DIE__ handler around a number of 
> > > remote calls on the client side.  After applying it here, I have been 
> > > using your strawman 1.31 release in production for the past month or so.
> > > 
> > > Let me know if you want me to re-send the patch or rationale for same?
> > > 
> > > 
> > > Steve
> > > 
> > > 
> > 
> 
> -- 
> ----------------------------------------------------------------
> Steven N. Hirsch       tie-line: 446-6557     ext: 802-769-6557
> 
> Staff Engineer                     Methodology Integration Team
> ASIC Product Development           IBM Microelectronics
> ----------------------------------------------------------------
> 

Reply via email to