The key question here, I believe, is what you forsee to be done with the data. Since you're not interfacing with the application but rather reading the files yourself, a DBD "driver" in your case would have to be a fullblown database engine, complete with SQL parser and all the dirty nitty gritty. Is such heavy duty data munging and close integration with Blaise forseeable that it makes that kind of effort worthwhile? I tend to think not so..
It would probably be better to write some Perl code to merely im- and export for these .bdb files, and dump the data in and out of a "real" database for your munging needs.
As far as reading non-textual data is concerned, Perl's unpack function is lots of very powerful magic and would fit your bill perfectly.Makeshifts last the longest.
In reply to Re: blaise and perl
by Aristotle
in thread blaise and perl
by aufrank
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |