Re: Merging DBD::RAM into DBI

Sven Dowideit <[email protected]>
Newsgroups gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

yup :)

https://metacpan.org/source/REHSACK/DBD-AnyData-0.110/README

(then search for 'RAM')

|  ||HISTORICAL NOTE: this module was formerly called DBD::RAM.  Its name|
|  ||was changed because many people were unaware that the module supports|
|  ||file operations in addition to in-memory operations.  See the Changes|
|  ||file for a description of changes since the last release of DBD::RAM.

Not to say that its a bad idea, but there is more up to date code to
tease apart in DBD::AnyData :/

The most complicated issue with DBD::AnyData is that is not written only
for DBI use,
the non-DBI AnyData module is useful by itself (and it does the heavy
lifting wrt IO).

Sven|


On 22/12/12 03:34, Jens Rehsack wrote:
> Hi all,
>
> I'd like to merge DBD::RAM into DBI for several reasons:
>
> 1) It's a tiny one without much dependencies, it should run fine
> with just DBI::Sql::Nano (or should)
>
> 2) I had an evil idea how to allow Pure-Perl drivers can work
> together in one instance like:
>
> DBI->connect( "dbi:DBM:", , , {
> sql_join_drv => "DBD::RAM", ... } );
>
> But there is something for testing required ;)
>
> 3) It currently doesn't get some love, even if it should get.
>
> Any comments?
>
> Cheers


- -- 
________________________________________
Professional Wiki Innovation and Support
Enterprise Support Contracts for Foswiki
Sven Dowideit          http://fosiki.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDU14YACgkQPAwzu0QrW+kyYQCdGxMFncZpz+GVwP2amnZfV8HO
2j0AoKrNkaS8rQcfRZEOE1iywCAFhmuu
=al5c
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.