Tim Bunce skrev: > A. What changes you'd like to see in the DBI API. > > B. What changes you'd like to see in the DBD API > (that's the DBI<->DBD interface). > 1) The Ingres Open/API has the possibility of doing async db-access, ie starting a database request and then at a later point in time either waiting for it to complete or just checking if it is completed yet.
It doesn't support threads (as far as I can see) or at least the DBD-layer would have to do some nifty footwork to support it. I don't know what the DBI API for this kind of functionality should be, but I think that it should at least be considered. 2) Better support for transactions. At some point I predict that the RDBMS vendors will come up with transaction handles, and we need somewhere to hold them - I foresee several concurrent transactions on the same database handle. 3) A way of getting all active children from a handle, eg all active $sth's in a $dbh. This is usefull when doing something potentially nasty to the $dbh (eg. committing or disconnecting) and you need to do something to all $sth's before - the only way out nnow is to error out with a suitable message to the user, and let them do whatever has to be done. > And, looking further ahead... > > C. How interested/motivated you are in working on a DBD for Parrot. I would love to find the tuits to do that. A good excuse to learn some parrot at last, after lurking on the mailinglists for years. -- Henrik Tougaard, DBD::Ingres.
