First of all, thanks to those of you who replied to my question. Very helpful.
At 3:18 PM +0000 11/23/04, Tim Bunce wrote:
You've got a lot of good advice from others. I'll just add that dbi-users would have been a more appropriate forum for this :) Tim.
Sorry.
At the time, I thought dbi-dev was more appropriate because mine wasn't so much an end-user question as something that could affect the development of DBI itself and its drivers.
How does one know where to draw the line between what is relevant for dbi-dev and what isn't?
The official description of dbi-dev gives an approximate idea:
Discussions among DBI/DBD implementors. You probably don't need to be on this list unless you are writing C code to interface Perl to some database. This list is for implementors only.
However, a lot of people contribute to the development of DBI/DBD besides those that own each module, and some modules have no C component. Is this list strictly for those who have their own DBD modules that they own? Or for those that provide assistence also?
While I don't run my own DBD module, I am closely interested in the development issues concerning the system, and I am working on modules that could constitute a comprehensive common test suite for drivers. My code primarily sits on top of the DBI interface rather than below it, but I don't really consider myself to be much more of an end-user than any of you are, assuming you use your own DBD modules to accomplish work.
So can I use dbi-dev to discuss issues that come up during the development of a test suite, which may require filling in some holes in the DBI interface or DBD implementations?
Here's a biggie ...
Does it ever happen that you get people posting to other lists such as poop-group or dbi-dev with issues that should be on dbi-dev?
Perhaps I will simply "play it safe" from now on and post all DBI-related discussions to other lists, such as poop-group and dbi-users. If any of them are relevant to DBI/DBD implementors, then hopefully they will be visible to them there.
Meanwhile, I will remain subscribed to dbi-dev, since it is very low traffic, but I will stick to replies to other topic threads, such as Tim's request to test the 1.46 release candidate, rather than starting my own.
-- Darren Duncan
