On Wed, Oct 08, 2008 at 10:52:42AM -0400, Michael G Schwern wrote:
>
> There's plenty of modules which need a database,
> and they all have to be configured differently and they're always a PITA when
> you first install and each and every time they upgrade.
>
> User setup can be dealt with by mak
David Cantrell writes:
> Smylers wrote:
>
> > It sounds scary to me. If I'm just installing a Perl module from
> > Cpan on a newly installed OS, which happens to still have default DB
> > connection permissions, I wouldn't expect the module's tests to
> > start making use of the DB without askin
On Thu, Oct 09, 2008 at 02:24:55PM -0400, Greg Sabino Mullane wrote:
>
> > > > ... I suppose it could also be somewhat easy to try out a few series
> > > > of basic/default credentials on localhost for engines like MySQL and
> > > > Postgres, and try to setup a test database from there.
> > >
> >
On Thu, Oct 09, 2008 at 06:10:30PM +0100, Smylers wrote:
> Greg Sabino Mullane writes:
>
> > > ... I suppose it could also be somewhat easy to try out a few series
> > > of basic/default credentials on localhost for engines like MySQL and
> > > Postgres, and try to setup a test database from there
Smylers wrote:
> It sounds scary to me. If I'm just installing a Perl module from Cpan
> on a newly installed OS, which happens to still have default DB
> connection permissions, I wouldn't expect the module's tests to start
> making use of the DB without asking.
Of course, a module author can d
> > > ... I suppose it could also be somewhat easy to try out a few series
> > > of basic/default credentials on localhost for engines like MySQL and
> > > Postgres, and try to setup a test database from there.
> >
> > That sounds more interesting.
>
> It sounds scary to me.
I don't think eithe
Greg Sabino Mullane writes:
> > ... I suppose it could also be somewhat easy to try out a few series
> > of basic/default credentials on localhost for engines like MySQL and
> > Postgres, and try to setup a test database from there.
>
> That sounds more interesting.
It sounds scary to me. If I'
Greg Sabino Mullane wrote:
>> It should be fairly easy for willing CPAN testers to setup any database
>> they like, and provide some connection information for throwaway tables
>> and data (assuming the test script WILL probably drop all tables in
>> there and dump its own crap there).
>
> This se
On Wed, Oct 08, 2008 at 10:17:31AM -0400, Greg Sabino Mullane wrote:
>
> > It should be fairly easy for willing CPAN testers to setup any database
> > they like, and provide some connection information for throwaway tables
> > and data (assuming the test script WILL probably drop all tables in
> >
> It should be fairly easy for willing CPAN testers to setup any database
> they like, and provide some connection information for throwaway tables
> and data (assuming the test script WILL probably drop all tables in
> there and dump its own crap there).
This seems of dubious usefulness, as the
On Wed, Oct 08, 2008 at 05:34:52AM -0700, Ovid wrote:
> >
> > A colleague of mine is working on a very interesting
> > module, but even though he could release a test suite
> > relying on sqlite, I thought it would be better to use
> > any configured database that was available on the
> > tester's
On Wed, Oct 08, 2008 at 01:17:16PM +0100, David Cantrell wrote:
> On Wed, Oct 08, 2008 at 10:56:27AM +0200, Philippe Bruhat (BooK) wrote:
>
> > Is there any way for a test suite to use the preferred database of a
> > tester? Something like a TEST_DATABASE_DSN, TEST_DATABASE_USERNAME,
> > TEST_DATA
--- On Wed, 8/10/08, Philippe Bruhat (BooK) <[EMAIL PROTECTED]> wrote:
> Is there any way for a test suite to use the preferred
> database of a
> tester? Something like a TEST_DATABASE_DSN,
> TEST_DATABASE_USERNAME,
> TEST_DATABASE_PASSWORD triplet that CPAN testers could set
> to enable
> testin
On Wed, Oct 08, 2008 at 10:56:27AM +0200, Philippe Bruhat (BooK) wrote:
> Is there any way for a test suite to use the preferred database of a
> tester? Something like a TEST_DATABASE_DSN, TEST_DATABASE_USERNAME,
> TEST_DATABASE_PASSWORD triplet that CPAN testers could set to enable
> testing on d
Hi,
Is there any way for a test suite to use the preferred database of a
tester? Something like a TEST_DATABASE_DSN, TEST_DATABASE_USERNAME,
TEST_DATABASE_PASSWORD triplet that CPAN testers could set to enable
testing on different databases?
A colleague of mine is working on a very interesting mo
15 matches
Mail list logo
