Bug #111414 for Test-postgresql: Removal of global %Defaults breaks backwards compatibility (v1,20)

Mon Jan 25 05:47:17 2016 SYSPETE [...] cpan.org - Ticket created

Subject:

Removal of global %Defaults breaks backwards compatibility (v1,20)

Just switched to working on a project which relies on old global %Defaults for setting initdb_args and so tests fail. Perhaps %Defaults should be reintroduced since adding to initdb_args is not possible since it can only be replaced completely and also to keep backwards compat?

Mon Jan 25 08:09:55 2016 TJC [...] cpan.org - Correspondence added

I really don't like the global singleton %Defaults. It's far from best practices. But.. keeping backwards compat is good too. :(

Mon Jan 25 08:09:55 2016 The RT System itself - Status changed from 'new' to 'open'

Mon Jan 25 12:26:13 2016 SYSPETE [...] cpan.org - Correspondence added

On Mon Jan 25 08:09:55 2016, TJC wrote: Show quoted text

> I really don't like the global singleton %Defaults. > It's far from best practices. > But.. keeping backwards compat is good too. :(

I've created a pull request which ties %Defaults so any package which uses Test::PostgreSQL and then reads from %Defaults will get a deprecation warning. https://github.com/TJC/Test-postgresql/pull/15 There may be better ways to achieve this but this at least works, keeps backwards-compatibility for anyone reading from %Defaults and also throws a deprecation warning.

Sun Jan 31 21:48:45 2016 TJC [...] cpan.org - Correspondence added

Fixed in 1.20_05 via your PR. Thanks.

Sun Jan 31 21:48:47 2016 TJC [...] cpan.org - Status changed from 'open' to 'resolved'