On 04/02/2011 20:00, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already existing SQL flag. I never got
around to it and Merijn reminded me today on #dbi. The change is
trivial and once implemented I will
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already existing SQL flag. I never got
around to it and Merijn reminded me today on #dbi. The change is
trivial and once
On 05/02/2011 12:29, Tim Bunce wrote:
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the already existing SQL flag. I never got
around to it and Merijn reminded me today on #dbi.
On 05/02/2011 12:54, Martin J. Evans wrote:
On 05/02/2011 12:34, Martin J. Evans wrote:
On 05/02/2011 12:29, Tim Bunce wrote:
On Fri, Feb 04, 2011 at 08:00:13PM +, Martin J. Evans wrote:
Tim,
At the LPW I think I promised to add connection and encoding trace
flags to DBI which add to the
2010/7/26 Tim Bunce tim.bu...@pobox.com:
On Fri, Jul 23, 2010 at 10:16:16AM +, Jens Rehsack wrote:
On 07/20/10 19:20, Tim Bunce wrote:
I can imagine at least 2:
1) Bundle::DBD::DBM
- requires DB_File and BerkeleyDB
- requires MLDBM, MLDBM::Serializer::JSON and YAML::MLDBM
-
On 03/02/2011 10:01, Tim Bunce wrote:
On Wed, Feb 02, 2011 at 03:52:00PM +, Martin J. Evans wrote:
[...]
So, I think DBI works fine right now (given slight pod change) and
don't want to complicate it or worse, break peoples existing code.
Great! :)
DBD:: Oracle on the other hand does