Re: Mysql::Simple

On Fri, 17 Sep 2004, Jeremy Zawodny wrote:

>On Fri, Sep 17, 2004 at 06:17:24PM +0100, Dan Bolser wrote:
>> 
>> I have made a perl module called Mysql::Simple which parses /etc/my.cfg
>> and ~.my.cfg to set up Mysql connection parameters. In case it dosn't find
>> a password it uses Term::ReadPassword to get the user to supply one.
>
>Can I suggest a naming change?  MySQL::Simple instead of Mysql?  Since
>MySQL is a real product name, using proper capitalization seems only
>fair and intuitive.

Great, MySQL::Simple it is.

>
>> I am looking for feedback, and perhaps a volunteer to help make this a
>> proper CPAN module.
>
>I might be able to help with that.

Naturally I wan't to help as much as I can, but I have no experience
packaging up a module for CPAN, and I guess this is relativly easy for
someone who knows what they are doing.

>> The befifit of this module is never writing another connection string, and
>> not worrying about where to put your password.
>
>Hey, that was one of the goals behind DBIx::DWIW too. :-)

:) I like the module. It looks good. I wouldn't want to try to reimplement
any of the nice features supported by your module in MySQL::Simple, as it
looks like you have done a good job on those important features. Also I
guess I should look at DBIx::Password to see if it more sensible than
calls to Term::ReadPassword.

However, I gues you can tell from the name, a big aim of MySQL::Simple is
that it it as simple as possible, doing the minimum amount of
functionality, and mimicking a true mysql application as much as possible
(by reading command line args).

So I guess there is still room for MySQL simple?

How should we/I procede? I can put the code somewhere, or I can read a
'cpan packaging module begginers guide / how-to / cookbook' and we can go
from there.

>Jeremy
>

Thanks very much for your support,
Dan.


-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]