I hope my reply comes across correctly. > Hi Jens and Sven, > > I understand that AnyData needs a reset. What is consensus if direction? > For my project I need to manage a big variety of source formats, so I'll be > willing to participate in redesign or coding of AnyData if need be. Otherwise > I'll have to dream up my own data format abstraction layer. > > There are generally four types of sources or formats in my environment > > Databases accessible through DBI > Databases accessible through command line binaries > Records based files, such as csv > Table based files, such as /etc/hosts, json etc. > > Any lessons we can stage from Augeas and it's concept of lenses? Or just > bridge > between Augeas and DBI?
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. Jonathan Otsuka
