Skip to content
Commits on May 2, 2010
  1. Match double quotes arround table name in select_regexp to support Po…

    committed
    …stgreSQL (ANSI actually).
Commits on Apr 6, 2010
  1. @sdsykes

    Add instructions for rails 3

    sdsykes committed
Commits on Apr 4, 2010
  1. @sdsykes

    bump version

    sdsykes committed
  2. @sdsykes
  3. @sdsykes
  4. @sdsykes
  5. @sdsykes

    Correct regexp to recognise optimisable queries to be rails 3 compati…

    sdsykes committed
    …ble. Bump vers in gemspec.
  6. @sdsykes

    Version bump to 1.0.6

    sdsykes committed
Commits on Mar 18, 2010
  1. @sdsykes
  2. @sdsykes
Commits on Mar 17, 2010
  1. @parndt
  2. @parndt
  3. @parndt

    Make this plugin compile on runtime instead on a rails system. This w…

    parndt committed
    …on't work outside of rails so isn't a complete solution yet.
Commits on Mar 11, 2010
  1. @sdsykes
Commits on Feb 15, 2010
  1. @sdsykes

    Support other platforms that MRI 1.8 by making compilation of the (MR…

    sdsykes committed
    …I18 only) extension conditional. Bump version to 1.0.5.
  2. @sdsykes
  3. @sdsykes

    Version bump to 1.0.5

    sdsykes committed
Commits on Jan 14, 2010
  1. @sdsykes
Commits on Dec 26, 2009
  1. @sdsykes

    Do not hold AR class objects in callsites because class reloading in …

    sdsykes committed
    …dev mode will be hampered (fixes issue 4)
  2. @sdsykes

    Version bump to 1.0.4

    sdsykes committed
Commits on Nov 26, 2009
  1. @sdsykes

    Doc updates

    sdsykes committed
  2. @sdsykes
  3. @sdsykes

    Version bump to 1.0.3

    sdsykes committed
Commits on Nov 23, 2009
  1. @sdsykes

    Increment version

    sdsykes committed
  2. @sdsykes
  3. @sdsykes

    Documentation updates

    sdsykes committed
  4. @sdsykes

    Version bump to 1.0.2

    sdsykes committed
Commits on Nov 8, 2009
  1. @sdsykes
Commits on Nov 7, 2009
  1. @sdsykes
  2. @sdsykes

    Version bump to 1.0.1

    sdsykes committed
  3. @sdsykes
Commits on Nov 6, 2009
  1. @sdsykes
  2. @sdsykes
  3. @sdsykes
  4. @sdsykes
Something went wrong with that request. Please try again.