CVS commit: pkgsrc/databases/p5-Jifty-DBI

[Stoned Elipot <seb%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   seb
Date:           Sun Aug 23 22:27:47 UTC 2009

Modified Files:
        pkgsrc/databases/p5-Jifty-DBI: Makefile distinfo

Log Message:
Update p5-Jifty-DBI from version 0.53 to version 0.58.

Pkgsrc changes:
- Perl 5.10, which includes version.pm, is now required by pkgsrc, hence
the dependency on devel/p5-version can be removed
- Set LICENSE

Upstream changes:
0.58 Tue Jul 14 03:21:21 EST 2009
- Possible incompatibilities:
    * Modules which use Jifty::DBI::Schema will have strict and warnings
      automatically applied to them.

- Features:
    * Jifty::DBI::Handle now has methods for supported_drivers,
      available_drivers, and is_available_driver.

- Fixes:
    * Remove unused _limit_clause method
    * Various error message improvements
    * Use ->new_item instead of ->record_class->new since it was a performance
        hit in Jifty
    * Avoid cals to ->new_item where possible

- Documentation:
    * Document connect's quirky return value

0.57 Tue May 19 08:02:03 EDT 2009
- Major bugfixes:
    * Use eval {} in Jifty::DBI::Handle's DESTROY block when manipulating DBI
        Alterations to the DBI object in the DESTROY block must be wrapped in
        an eval {}, as object destruction order is not guaranteed during
        global destruction, and this interacts poorly with DBI's tie'd object.
    * During DESTROY, don't explicitly disconnect a dbh set InactiveDestroy
        The InactiveDestroy flag on DBI objects prevent them from being
        implicitly disconnected when they go out of scope -- for example, in
        the case where a process has forked, and two processes hold the socket
        open.
        However, it does not prevent them from being _explicitly_
        disconnected, as we were doing in Jifty::DBI::Handle's DESTROY method.
        This caused InactiveDestroy to never kick in, causing either a shared
        socket, or two closed handles after a fork.  We prevent this by having
        Jifty::DBI::Handle respect InactiveDestroy in its DESTROY method.
    * Do not use Scalar::Defer defaults for columns' defaults in the db

- New features:
    * Add a display_length attribute on columns
    * add schema manipulation tables: rename_column and rename_table
    * If a column's default is a record, call its id method

- Fixes:
    * Improve SQL error message and avoid its duplication
    * Pull the input_ and output_filters out of the instance hash

- Tests:
    * Added a unit test for the SaltHash filter
    * use drop_table_if_exists in tests
    * add drop_table_if_exists in t/utils.t
    * unconditionaly drop tables for testing
    * test rename_table
    * add tests for rename_column
    * SaltHash test does not need an is_deeply()
    * Don't explicitly disconnect the handle, DESTROY handles it better
    * Test for warnings instead of letting them leak into the test output


To generate a diff of this commit:
cvs rdiff -u -r1.3 -r1.4 pkgsrc/databases/p5-Jifty-DBI/Makefile
cvs rdiff -u -r1.2 -r1.3 pkgsrc/databases/p5-Jifty-DBI/distinfo

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.