Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Branch: master
Commits on Oct 23, 2010
  1. in-memory db

    * db is created in memory, nothing on disk (so we can skip creating fake db in
    temp file)
    * move schema creation to testapp
  2. require DBD::SQLite or skip

  3. add tests:

    * simple application with some routes
    * test to interact with the DB via Dancer
Commits on Sep 28, 2010
  1. @bigpresh

    Preparing version 0.09 for release.

    bigpresh authored
    This is the multi-DB support previously released as 0.08_01, with a few minor
    Thanks go to Igor Bujna for proposing this feature and providing patches.
    Thanks Igor!
Commits on Sep 14, 2010
  1. @bigpresh

    Don't attempt to call Dancer::Loggger as a class method.

    bigpresh authored
    "Dancer::Logger" is not generally a helpful debug message :)
  2. @bigpresh

    Handle multiple named database connections.

    bigpresh authored
    This is thanks to Ignor Bujna who supplied the original code for this - thanks
    I've refactored it slightly and added some documentation.
    This allows you to say database($name) where $name is the name of a connection
    defined in your configuration file, so multiple connections are easily handled.
    Since this is a fairly major change, I'll release it as a dev release for
    testing first.
  3. @bigpresh

    Make the SQLite DWIMmery from 0.07 actually work.

    bigpresh authored
    I'd made a stupid logic error which meant it had no chance of working properly.
Commits on Sep 6, 2010
  1. @bigpresh
  2. @bigpresh

    Preparing 0.07 for release

    bigpresh authored
  3. @bigpresh

    Translate database to dbname for SQLite users.

    bigpresh authored
    DBD::SQLite requires the database name (filename) to be passed as 'dbname', not
    'database'.  (The DBI docs recommend that all DBD::* drivers should understand
    'database', but DBD::SQLite currently doesn't).
    Make things easier for users by translating database to dbname if connecting
    using the SQLite driver.
  4. @bigpresh

    Separate extra DSN params with semi-colons.

    bigpresh authored
    When forming a DSN, colons should be used for "dbi:driver:", but semi-colons
    should be used to delimit additional parameters (database, host, port).
    Thanks to Steve Atkins for reporting this in RT #61089.
    Also, documentation update to relect the use of $dbh->ping.
Commits on Jun 15, 2010
  1. @bigpresh

    Stupid typo in documentation for features added in 0.05.

    bigpresh authored
    Wish I'd spotted this before releasing 0.05, rather than just after!
  2. @bigpresh

    Accept DBI connection params, and support on-connect queries.

    bigpresh authored
    Applying patch from Igor Bujna ading the ability to provide parameters to be
    passed to the DBI->connect call, e.g. RaiseError or AutoCommit, and also the
    ability to provide a list of queries which should be performed immediately upon
    connection to the database.
    Thanks Igor!
    In documenting these changes, I also improved the existing documentation
Commits on May 20, 2010
  1. @bigpresh

    Implement our own check on database connection where needed.

    bigpresh authored
    If DBD driver doesn't implement ping(), do our own simple test (attempt a simple
    This avoids unnecessary and expensive reconnects when using a DBD driver without
    a ping() implementation.
    Log a debug message when reconnecting.
    This release seems to fix an issue Tadzik was experiencing whilst using
    DBD::SQLite, and receiving a warning when the old DB connection went out of
      Issuing rollback() due to DESTROY without explicit disconnect()
Commits on May 19, 2010
  1. @bigpresh

    If we need to reconnect, call disconnect on old handle first.

    bigpresh authored
    This is unlikely to achieve much, but it doesn't hurt to make sure.
    A user was experiencing warnings when using SQLite, stating:
        Issuing rollback() due to DESTROY without explicit disconnect()...
    This might, possibly, help with that.  If not, it won't hurt.
  2. @bigpresh

    Implement our own connection check when needed.

    bigpresh authored
    If the DBD::* driver doesn't implement its own ping() method, then perform our
    own connectivity check by performing a very simple query.
Commits on May 17, 2010
  1. @bigpresh

    Set $last_connection_check upon connection.

    bigpresh authored
    This avoids a warning emitted when using newer Dancer versions, where
    $last_connection_check was being used in comparison whilst still not yet
    Thanks to tadzik for reporting this on the Dancer IRC channel.
Commits on Apr 18, 2010
  1. @bigpresh
Commits on Apr 15, 2010
  1. @bigpresh

    Better description in name.

    bigpresh authored
    (It provides DB connections for Dancer apps, not Dancer itself.)
Commits on Apr 14, 2010
  1. @bigpresh

    Missing underscore.

    bigpresh authored
  2. @bigpresh

    Fix muppetry.

    bigpresh authored
  3. @bigpresh

    Correct dependencies.

    bigpresh authored
  4. @bigpresh
  5. @bigpresh

    Update Changes and README.

    bigpresh authored
  6. @bigpresh

    Implement _check_connection.

    bigpresh authored
    use $dbh->ping to check for connectivity.
    DBI provides a default ping method which returns 0 but true; if we get that, the
    driver in use doesn't implement ping(), so we may need to do something ourselves
    to handle it.  Perhaps try a 'select 1' query?
  7. @bigpresh

    get_connection / check_connection are private and should not be calle…

    bigpresh authored
    …d directly.
    So, prefix with _.
  8. @bigpresh
  9. @bigpresh

    Documentation improvements.

    bigpresh authored
  10. @bigpresh

    Initial development of Dancer::Plugin::Database.

    bigpresh authored
    Not yet ready to use.
Something went wrong with that request. Please try again.