On Tue, Dec 14, 2004 at 06:24:40PM -0800, Jonathan Leffler wrote:
On Tue, 14 Dec 2004 16:47:39 +, Tim Bunce [EMAIL PROTECTED] wrote:
On Tue, Dec 14, 2004 at 07:08:08AM -0800, Jonathan Leffler wrote:
I had certainly managed to miss this change - which could easily
account for some of
Sorry for this flurry of half-researched questions... :-(
I'll probably be able to submit another patch to DBI::DBD.pm out of this.
On Wed, 15 Dec 2004 10:11:57 +, Tim Bunce [EMAIL PROTECTED] wrote:
On Tue, Dec 14, 2004 at 06:24:40PM -0800, Jonathan Leffler wrote:
On Tue, 14 Dec 2004
On Wed, Dec 15, 2004 at 07:27:59AM -0800, Jonathan Leffler wrote:
Sorry for this flurry of half-researched questions... :-(
I'll probably be able to submit another patch to DBI::DBD.pm out of this.
Great! Thanks.
Tim.
p.s. Patch against subversion if possible. If not grab the latest
from
At 12:28 PM + 12/15/04, Jeff Zucker wrote:
I am thinking of extending the DBD::AnyData DSN in three ways and
would appreciate comments. If these are good, there will be
equivalent changes for DBD::DBM and DBD::CSV.
I can think of an additional change that would be useful while you're at it.
At 1:12 PM + 12/15/04, Jeff Zucker wrote:
Unfortunately, I don't see any way to do that. Some DBM
implementations have different file naming conventions. For AnyData
and CSV, files can be named anything. Even if we could recognize
the names of the files we wouldn't necessarily know which
At 2:13 PM + 12/15/04, Jeff Zucker wrote:
Darren Duncan wrote:
How much trouble would it be to actually look inside each file?
Lots of trouble. Since DBD::DBM supports many DBM types and many
MLDBM types, one file might be SDBM, another Berkeley_DB, etc. and
each of those might use MLDBM
