Permalink
Commits on Mar 17, 2011
  1. Timestamp v0.43.

    committed Mar 17, 2011
  2. Remove mention of `Try::Tiny::catch`.

    It doesn't work for passing a catch handler to the methods anymore.
    committed Mar 17, 2011
Commits on Jan 31, 2011
  1. Add per-driver post-connection handling.

    Use it to teach MySQL to set `mysql_auto_reconnect` to false, to keep MySQL's
    auto-reconnection feature from interfering with DBIx::Connector's
    auto-reconnection functionality in `fixup` mode. Thanks to Karen Etheridge and
    Peter Rabbitson for the report.
    committed Jan 31, 2011
  2. Default RaiseError to true.

    It's important for the execution methods that the database handle raise
    exceptions on errors so that they can be properly handled. This is especially
    true for C<txn()> to get automatic rollback on failure. So set `RaiseError`
    to true if neither it nor `HandleError` has been specified. And document
    how important it is that these attributes be set correctly.
    
    While at it, document that DBIx::Connector also chagnes the default value of
    `AutoInactiveDestroy`.
    committed Jan 31, 2011
Commits on Dec 17, 2010
  1. Increment version to 0.43.

    committed Dec 17, 2010
  2. Timestamped for 0.42.

    committed Dec 17, 2010
  3. Fix bug where catch blocks did not propagate exceptions.

    If you threw an exception from a catch block, it would not be detectable
    from outside:
    
        eval {
            $conn->run(sub { die 'WTF' }, catch => sub { die 'OMG!' });
        };
        if (my $err = $@) {
            say "We got an error: $@\n";
        }
    
    In this example, the `if` block would never be called, because even though the
    catch block threw an exception, $@ was not set. This could be terribly
    annoying, as you can imagine. I was being a bit too clever about localizing
    `$@`, but did so with the scope much too broad. This patch uses a much tighter
    scope to localize `$@`, so now it should propagate properly everywhere.
    committed Dec 17, 2010
Commits on Dec 8, 2010
  1. Add 0.42 to Changes.

    committed Dec 8, 2010
  2. Increment version to 0.42.

    committed Dec 8, 2010
  3. Timestamp for 0.41.

    committed Dec 8, 2010
  4. Add `disconnect_on_destroy()`.

    Suggested by John Siracusa. Closes #6.
    committed Dec 8, 2010
Commits on Nov 4, 2010
  1. pod fixes

    karenetheridge committed Nov 4, 2010
Commits on Sep 17, 2010
  1. Increment version to 0.41.

    committed Sep 17, 2010
  2. Timestamp for 0.40 release.

    committed Sep 17, 2010
  3. Increment to version 0.40.

    committed Sep 17, 2010
  4. Require Test::Pod.

    And update link to the GitHub repository to be a nice link.
    committed Sep 17, 2010
Commits on Sep 9, 2010
  1. Email bug reports, too.

    committed Sep 9, 2010
  2. I kant spel.

    committed Sep 9, 2010
Commits on Sep 3, 2010
  1. Rollback on disconnect was removed.

    So remove the docs that say that.
    committed Sep 3, 2010
Commits on Aug 30, 2010
  1. Give credit where credit is due.

    committed Aug 30, 2010
  2. Simplify `DESTROY()`.

    * `DESTROY()` no longer pings the database or rolls back transactions. It now
      simply calls `disconnect`. This avoids warnings during global destruction,
      and doesn't seem necessary anyway, as the DBI does these things during
      global destruction (and always has).
    * `DESTROY()` now clears `CachedKids`, following the precedent of DBIx::Class.
       May not be needed for recent-ish drivers, but seems harmless and it's nice
       to avoid warnings were possible.
    * The `connected()` method no longer `local`ly sets `RaiseError`. It instead
      leaves that to the drivers (currenly only Driver::Oracle).
    committed Aug 30, 2010
Commits on Aug 6, 2010
  1. Alphabetize.

    committed Aug 6, 2010
  2. Set `AutoInactiveDestroy` with DBI 1.614 and up.

    Set `AutoInactiveDestroy` on connect with DBI 1.614 and higher, unless it is
    explicitly set in the attributes. This makes things even safer in a forking
    environment, preventing a parent process from getting disconnected when a
    child exits without using the connection. The reports from Peter Rabbitson and
    Aran Deltac and subsequent discussion with Tim Bunce led to the addition of
    this attribute in DBI 1.614, which is now the recommended version of DBI.
    committed Aug 6, 2010
Commits on Jul 29, 2010
  1. Document use of `wantarray` in blocks.

    Also added tests to make sure it works for `svp()` and `run()` in addition to
    `txn()`, and updated `Changes`.
    committed Jul 29, 2010
  2. Fix context for _exec

    yko committed Jul 29, 2010
Commits on Jun 4, 2010
  1. Timestamp for 0.35 release.

    committed Jun 4, 2010
Commits on May 24, 2010
  1. Add a scoping block around the execution of the blocks passed to `run…

    …()`,
    
    `txn()`, and `svp()`. This prevents an app from exiting when a user returns
    from the block via the `next` or `last` keyword, which in turn prevented
    transaction management code from running.
    committed May 24, 2010
Commits on May 3, 2010
  1. Increment version to 0.35.

    committed May 3, 2010
  2. Timestamp for 0.34

    A few minor code tweaks. Notably, only disable `with()`'s warnings when our
    own tests are running. They should be quite visible for anyone else's tests.
    committed May 3, 2010