Skip to content
Commits on May 12, 2009
Commits on Apr 16, 2009
  1. Moving the database name out of the TimestampRename processor and int…

    committed Apr 16, 2009
    …o its own processor called PrependDatabaseName.
Commits on Apr 9, 2009
  1. Major refactoring.

    committed Apr 9, 2009
  2. Merge commit 'clint/master'

    committed Apr 9, 2009
  3. Adding the file argument to the process method of the PostProcessBase…

    committed Apr 9, 2009
    … and adding some comments about subclasses.
Commits on Apr 8, 2009
  1. adding a gitignore

    Clinton Ecker committed Apr 8, 2009
  2. Merge branch 'master' of git://github.com/robhudson/dumpy

    Clinton Ecker committed Apr 8, 2009
    Conflicts:
    	dumpy/dumper.py
  3. @brosner

    Added PostgreSQL support.

    brosner committed with Clint Ecker Apr 9, 2009
    Signed-off-by: Clint Ecker <clint@arstechnica.com>
  4. @brosner

    Added PostgreSQL support.

    brosner committed with Apr 9, 2009
    Signed-off-by: Rob Hudson <rob@tastybrew.com>
  5. @brosner

    When there are no database postprocessing then make it a no-opt.

    brosner committed with Apr 9, 2009
    Signed-off-by: Rob Hudson <rob@tastybrew.com>
  6. @brosner

    Made boto optional.

    brosner committed with Apr 9, 2009
    Signed-off-by: Rob Hudson <rob@tastybrew.com>
  7. Added command line switches (--database, --verbose, --all), proper lo…

    Clinton Ecker committed Apr 8, 2009
    …gging, and an option you can put in the [database] config section to specify whether or not the TimestampRename will plop in the name of the db into the output file (not sure if this is the best way to do this).
Commits on Apr 7, 2009
  1. Lots of refactoring.

    committed Apr 7, 2009
    Let each subclass handle its own config processing.  Moving towards chainable post processors for things like file renaming with timestamp, file copy, bzip output, copy to S3, etc.
Commits on Apr 5, 2009
  1. Beginnings of script.

    committed Apr 5, 2009
  2. README with ideas.

    committed Apr 5, 2009
Something went wrong with that request. Please try again.