DBIWrapper 0.23 now available

James A. Pattie — Sat, 19 Nov 2005 04:58:29 -0000

This is a bug fix in regards to the new Sybase support.

Adds a new xml output format, but no parsing support yet.

DBIWrapper 0.22 adds Sybase support!

James A. Pattie — Sat, 15 Oct 2005 05:39:04 -0000

DBD::Sybase is now officially supported and the getData... methods (getDataArray, getDataArrayHeader, getDataHash, getDataHashHeader) all know how to properly handle the possible multiple result sets that Sybase can return.

Added getID() to return the ID of the just inserted row.

DBIWrapper 0.21 available for consumption

James A. Pattie — Fri, 01 Apr 2005 15:48:08 -0000

Version 0.21 of the DBIWrapper perl module provides a revamped error handling infrastructure modeled after the error handling in the Portal::Base code developed in the PCXPortal project.

This was actually done several months ago and got pushed into the background and I forgot about releasing it until I noticed a server updating to a new version of the software from our unstable deb repository. Since everything seems to be working as desired, I've released it. Let me know if any bugs crop up. :)

Get the debs from http://www.pcxperience.org/

DBIWrapper 0.20 adds readHTML() method!

James A. Pattie — Wed, 30 Jun 2004 20:24:11 -0000

DBIWrapper 0.20 is now available for general consumption.

The major change is the addition of the readHTML() method which returns an html snippet containing the output of the specified sql select statement. The generated html is highly customizable via CSS.

The minor changes are the addition of boolean support functions to convert from 1/0 to true/false.

You can get debs from http://www.pcxperience.org/index.html#debian-apt

DBIWrapper 0.19 available

James A. Pattie — Tue, 16 Mar 2004 21:10:39 -0000

DBIWrapper 0.19 fixed some debian packaging dependacy issues where I was suggesting the C versions of libdbd and libdbi, not the perl versions.

I also udpated the methods that it makes sense to only accept a single argument and use the other defaults, to work in the single argument mode is the value, else do pass by name.

Ex: setError(errorString => "This is an error");
can now be done as
setError("This is an error");

The major affected methods were:
read, readXML, write, setError

See the man page for more details.

DBIWrapper 0.17 provides XMLParser module

James A. Pattie — Mon, 18 Mar 2002 21:38:59 -0000

DBIWrapper 0.17 now provides the XMLParser module which allows easy parsing of the XML generated by readXML(). This module relies on XML::LibXML, but does not require it to install the DBIWrapper package.

There were other minor updates and tweaks. See the Changelog for more details.

0.16 provides XML output capabilities!

James A. Pattie — Mon, 24 Dec 2001 18:19:46 -0000

DBIWrapper 0.16 has a new method - readXML(). This method allows you to have your SELECT statement be returned as an XML document rather than just the DBI sth handle to work with.

See the man page for documentation on how to use it. The web site will be updated shortly with usage info also.

0.15 fixes some errors when DESTROYing the DBIWrapper

James A. Pattie — Mon, 22 Oct 2001 23:40:19 -0000

Better error handling and trapping is now implemented in the close and DESTROY methods so that you don't get the following message in your apache log file, etc.:

Can't read $DBI::errstr, last handle unknown or destroyed at /usr/lib/perl5/site_perl/5.6.0/DBIWrapper.pm line 260 during global destruction.

Even more error output improvements

James A. Pattie — Sat, 08 Sep 2001 19:54:30 -0000

The plug arrays contents are now output in 'xxx', 'yyy', etc. format instead of 'xxx yyy' format. It will make determining what you passed in much easier.

Improved Debug Info on Errors

James A. Pattie — Mon, 23 Jul 2001 19:15:45 -0000

You can now specify the level of verbosity with which errors output the configuration settings of the DBIWrapper Object. The logLevel variable now allows you to turn off debug info (same as previous versions) or to incrementally turn on displaying of the configuration settings. The incremental levels are to keep potentially secret info hidden from the normal user while at the same time allowing them to give better feedback than an error occured. See man page and Changes file in version 0.13 for more details.

Recent posts to news