Re: AnyData open API

Am 15.11.2013 um 02:00 schrieb [email protected]:

> On Nov 14, 2013, at 1:09 AM, Jens Rehsack <[email protected]> wrote:
>>> 
>>> I just started looking into AnyData since I didn’t like all the work I was doing to use the template feature of unpack then while processing building a SQLite in-memory/file DB. I am thinking DBD::AnyData would be better and easier to maintain than what I have built 
>>> 
>>> I notice DBD::AnyData doesn’t work with DBI > 1.622. I am willing to help but not sure where to start. I may try to build a proof of concept from an older DBI to see if it will be any faster/easier to maintain that what I am doing now.
>> 
>> I would recommend 1st to join IRC - at irc.perl.org in #dbi channel.
>> If this is an absolute no-go, maybe a Hangout on Google+ would work better?
> 
> I didn’t know there was a #dbi channel! I thought #dbix-class was the only dbi channel. I have joined I am d^_^b or dj_goku or johnny5. :D

You must be somewhere completely different. I’ve looked for several days and don’t see you.
But: I’m kind of blind from time to time - please feel free to highlight me ([Sno]) or
probably (H. Merijn Brand) Tux or vanHoesel (Theo van Hoesel). The introductional topics they
all know and they know how to contact me (in doubt).

>> However - the first step should be to read the concept and api of
>> DBI::DBD::SqlEngine::(Table|Data)Source. I would favor this API even for
>> AnyData and it’s storage backends.
> 
> Alright looking at this now.
> 
>> Let’s together develop an API on-top of it for parsing, if necessary.
> 
> Alright this sounds good. I have no idea where to even start, but I’ll try to help/learn!

Start should be lib/DBI/DBD/SqlEngine.pm - read the developer and howto docs first.

>> When AnyData got rid of the internal Tie stuff, a reintegration of
>> DBD::AnyData into DBD::File will be a smooth way.

Cheers
-- 
Jens Rehsack
[email protected]