Skip to content
Commits on May 13, 2015
  1. @jamesrusso
  2. @jamesrusso

    update logic for eval.

    jamesrusso committed
  3. wrap ping in eval.

    root committed
Commits on Apr 30, 2015
  1. Update Changes

  2. Bump version to 0.09

  3. Merge pull request #61 from hvoers/master

    use an on_plugin_import block
Commits on Mar 14, 2015
  1. @hvoers

    use an on_plugin_import block

    hvoers committed
    This makes $dsl->database callable from other plugins.
Commits on Mar 13, 2015
  1. @ambs

    Fix docs

    ambs committed
Commits on Feb 8, 2015
  1. Bump dev release version, another try at cpantesters.

    cpantesters seriously kicks an enormous amount of arse.
    Being able to have your code tested on a whole multitude of Perl versions across
    a wide range of platforms, easily and for free, is so awesome.
  2. Uh, actually sort by keys here.

    I refactored this to use each() to get the keys and values together, but I'd
    wanted to do them in alphabetical order for the reasons mentioned in the last
  3. Use keys in alphabetical order for predictability

    Before, when adding keys & values to SQL, they were added in the order that
    keys() & values() return them - which is unpredictable across Perl versions and
    even individual executions, so could lead to subtle oddness, interfering with
    any clever schemes people may be using to group different queries by number of
    executions, and also makes testing hard, as I can't predict exactly what the
    resulting SQL should be (without re-implementing some of the generation logic
    within the test code, which I'd rather not, as subtle bugs could end up in both,
    and therefore wouldn't be caught by the test).
Commits on Feb 7, 2015
  1. Merge pull request #60 from bigpresh/feature/scalarref_for_function_c…

    Scalarrefs for verbatim values (for SQL function calls etc)
Commits on Jan 30, 2015
  1. Include sqlgen tests in plan.

    Define the sqlgen tests along with the others, then declare our plan, then start
  2. Expect no space here.

    This passes now, showing the feature was implemented right \o/
  3. Don't add scalarref values to bind params.

    If you've supplied a scalarref to be interpolated into the VALUES() as-is, it
    shouldn't also get added to the @bind_params.
  4. Support scalarrefs for untouched data in INSERTs.

    This lets you say e.g.:
    $handle->quick_insert('tablename', { foo => 'bar', timestamp => \'NOW()' });
    ... and the scalarref will go into the query as-is (so be careful about SQL
    injection - if you've asked the module to put it in as-is, it will, and can't
    protect you...)
  5. Tests for SQL generation

    Call _generate_sql() with a variety of inputs and test that the resulting SQL is
    as we expect.
  6. Handle SELECT queries with no WHERE clause provided.

    (Previously you had to provide a WHERE clause as {})
    ... not 100% sure I want this; it could make it easy to accidentally select all
    rows when you didn't mean to?
    Also, don't have a spurious extra space at the end of a SELECT query generated
    without a WHERE clause (or a double space if there is one)
  7. Fix indentation

Commits on Dec 29, 2014
  1. @ambs

    RT #101180

    ambs committed
Commits on Oct 13, 2014
  1. @ambs

    Fix dep

    ambs committed
  2. @ambs


    ambs committed
  3. @ambs

    Fixed t/01-basic.t

    ambs committed
  4. @ambs
  5. @ambs

    Added dsn_extra options

    ambs committed
Commits on Sep 1, 2014
  1. @ambs

    metadata for metacpan

    ambs committed
Something went wrong with that request. Please try again.