On Fri, Jan 30, 2004 at 03:19:45AM +0000, Harry Jackson wrote:
> Harry Jackson wrote:
>
> >Some of the code is only half finished ie We can connect and prepare but
> >not execute and fetch.
> >
> >Watch this space.
>
> We can now execute and fetch as can be seen from the bit of code I just
> posted. I am now working on handling multiple database/statement handles.
>
> I am also very open to suggestions about what people want to see here.
> If there are no suggestions I will just continue along as I am doing and
> it will probably all need to be changed when we start getting some
> feedback. If you think of me as your humble servant start firing
> questions/abuse and I will see what I can do.
>
> Some questions of my own:
>
> 1. Where are we going to put all the source.
>
> Thoughts:
> I am asking this because I am not sure that the Parrot source tree is
> the correct place to put it (neither is Tim). There are various reasons
> for this which I am sure Tim is bored explaining, not least of which
> will be namespaces etc.
>
> I am able to create a source tarball and hang it off my website but this
> if it happens should be a temporary measure and you will still need to
> have the Parrot source which is unavoidable.
I'm in the process of moving the DBI source to Subversion hosted by perl.org.
I think that would be a good home for DBDI as well.
> 2. What are people expecting/wanting to see first.
>
> Thoughts:
> At the moment I am rummaging around having a whale of a time doing what
> I _think!_ is correct. This is not necessarily a good idea so we really
> need some people to start making suggestions as to what they want to see
> done first. We also need some discussion on the Parrot DBDI and what
> people would like to see in it.
1. A clean stable application API as close to the DBI as practical.
That means:
Method names, parameters, return values as per DBI
Opaque handles (I think ".sym pmc dbh" will work
rather than a named reference type I suggested earlier)
Method calls (though if IMCC will get a clean syntax for them soon
it maybe best to wait and avoid the messy name mangling meanwhile.)
Get as close to my "design notes" (reposted this morning) as possible.
eg set_err(), err(), errstr(), new_child() get_row_array() etc
2. Make example less hard coded:
take dsn, user, password from command line
loop, asking for sql then execute, fetch, loop.
3. Some docs for "How to get started with Parrot and IMCC" that just lists
pointers to other docs plus a walk-through to get setup:
fetch parrot from <url>
unpack, cd, configure, build, install
these files are the dbdi source ...
run this command to execute the dbdi example
So newcomers can hit the ground running.
4. An NCI interface for mysql would greatly increase the potential early userbase.
5. Get into subversion as soon as it's available
I've asked Ask & Rob at perl.org to set it up.
Anyone wanting access should start by geting an account at auth.perl.org
Tim.
