At 1:02 PM +0000 12/27/03, Harry Jackson wrote:
Being fairly new to parrot and probably naive I can see a few different ways of doing this.
A C wrapper ie: parrot/classes/parrotdbi.pmc etc A C wrapper ie: parrot/dynclasses/parrotdbi.pmc etc A loadable pasm function library that uses the current libpq/(other libs) and available available ops.
I'd go with option 3, the loadable pasm library that uses the current libpq. I think that, right now, there's no need for anything else. That may turn out to be incorrect, but if so we can try Plan B. (Which involves either extending Parrot or getting the C extension stuff working)
OK. I will start on it now. I will probably have lots of questions while doing this.
Tim's right -- dodge the DBD/DBI names for right now. We're going to have enough of a headache with those later, what with there being both Ruby and Perl versions that use it. (Possibly Python too, I'm not sure)
I was only using them as examples. I will leave them pretty generic ie for the time being.
> getting back a full row as an array, getting back a full
row as a hash, and stuff like that. Nothing fancy, and nothing that high-level, but enough to work the basics without quite as manual work as the current libpg requires.
This'll probably be the basis for the DB driver interface for Parrot's DBI library, so this is your chance to make a mark. :)
Cheers for the opportunity.
Always happy to pass on work to other people. :)
As soon as I have a something of worth I will post the details.
H
