in reply to Thread and Fork Safe DBI and DBD::mysql replacement
I have a few quick comments:
It's not clear how this is to be used. Is it a DBD class, which can be accessed from within the normal DBI interface, a wrapper around an existing DBI handle, or is it a parallel mechanism that should be used separately?
Also, the name is much too general. Consider naming it DBD::MySQL::Threadsafe if it is a legitimate DBD subclass, or DBIx::ThreadSafe::MySQL if it's a wrapper.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Thread and Fork Safe DBI and DBD::mysql replacement
by Vautrin (Hermit) on Feb 07, 2004 at 00:30 UTC |