On Thu, Jan 03, 2002 at 12:39:26PM +0000, Matt Sergeant wrote: > Hi Tim, > > Not much I can say really except I think it seems extremely coherent, and > compliant with KISS, and well, you know I like the general concept :-)
:-) > On Thu, 3 Jan 2002, Tim Bunce wrote: > > The logic for mapping a connection into a hierarchy of classes > > will be extensible and overridable so that new or special cases > > can be handled, such as considering/including the database version. > > This is good. It's the one thing I'm aware of that's really missing from > AnyDBD. > > One thing to consider though might be some sort of backwards compatibility > plan - i.e. so we can say "Well if you *don't* want to upgrade DBI, you > can use AnyDBD to achieve the same result this way..." Doesn't seem worth it. I can't see any good reasons not to upgrade :) > Oh, and you might want to change to DBI 2.x, as this may seem a pretty > radical breakthrough for a lot of people. I hope it is, but it's fully compatible (if you ignore the odd rare case I hightlighted the other day) so I'll just bump the minor version as usual. I'll keep v2.0 for more radical internal surgery - such as when drivers need to be recompiled due to changes in the internal structures - which may happen as part of changing prepare() and adding in preparse(). Cynics might observe that v2.0 is likely to arrive around the same time as a new edition of the Programming the Perl DBI book - but that would be pure coincidence, of course :) Tim [who isn't even thinking about a new edition, yet] p.s. Ah yes, my crystal ball is glowing to remind me to mention that v3.0 will arrive around 2003-04-01 and be compatible with Perl6 ;-)
