FAQ
Hi,

first one is a tiny one - and might be a no-brainer ;)
Since AnyData2 is a bit more complicated than CSV and DBM (even if
DBM is on a good way ...), setting options per table is an
important feature for DBD::AnyData2.

I thought about something like:

$dbh->set_table_options( "north", { ad2_archive => ..., ad2_in_progress => ..., ... } );

Both options are for a concrete customer storage backend - so they
might be named "ad2_storage_..." or API should be

$dbh->set_table_options( "east", {
     ad2_storage => {
        archive => ...,
        in_progress => ...,
        ...
     },
     ad2_format => {
         ignore_missing_trailer => 1,
        ...
     } );

This one should make ad_import() call obsolete - for DBD::DBM we already
have the requirement. As a bonus, such an API could be the first step
in the direction of a dictionary (we already want that feature ^^).

How could such a feature look like for DBD::DBM, especially for dbm_storage
set to berkelydb?

Cheers
--
Jens Rehsack
rehsack@gmail.com

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 1 | next ›
Discussion Overview
groupdbi-dev @
categoriesperl
postedJan 27, '15 at 9:23a
activeJan 27, '15 at 9:23a
posts1
users1
websitedbi.perl.org

1 user in discussion

Jens Rehsack: 1 post

People

Translate

site design / logo © 2019 Grokbase