Commits on Feb 9, 2012
  1. We added a "--dump" flag to "migrations apply" that dumps the content…

    …s of the schema into the provided "schema_file" and made the migration commands raise appropriate Exceptions instead of just silently failing.
    Frank Hines & Ketema Harris committed Feb 9, 2012
  2. BUG: If the file doesn't exist (as it wouldn't yet in "migrations cre…

    …ate"), the "base.path()" function raises an Exception.
    Frank Hines & Ketema Harris committed Feb 9, 2012
  3. We wanted failures to be more obvious, particularly when the Exceptio…

    …n message didn't make sense...
    Frank Hines & Ketema Harris committed Feb 9, 2012
Commits on Dec 12, 2011
  1. @al-the-x

    Distutils complained about my use of "provides", and it doesn't seem …

    …to recognize the "requires" option, either. Otherwise, fairly successful distro.
    al-the-x committed Dec 12, 2011
  2. @al-the-x
  3. @al-the-x
  4. @al-the-x
  5. @al-the-x
  6. @al-the-x

    Significant refactoring in progress...! In order to get the sub-comma…

    …nd parsing working correctly, I had to refactor most of the base module into functions. :/
    al-the-x committed Dec 12, 2011
Commits on Dec 8, 2011
  1. @al-the-x
  2. @al-the-x
  3. @al-the-x

    This should permit me to load the sub-commands dynamically. I know th…

    …at "argparse" handles sub-commands, of course, but this is just easier for a first go.
    al-the-x committed Dec 8, 2011
  4. @al-the-x

    I moved the "migrations" module out of bin so that I could start pack…

    …aging it for distutils. That broke all those symlinks, obviously.
    al-the-x committed Dec 8, 2011
Commits on Nov 22, 2011
  1. @al-the-x

    I needed some branching logic within "apply" that I really didn't wan…

    …t to implement in Python, so I made a "migrate()" stored procedure in the "migrations" schema to handle that logic for me. This simplified my "apply" command significantly... And taught me a lot about PL/PgSQL. O_O
    al-the-x committed Nov 22, 2011
  2. @al-the-x

    There were still some references to the "migrations" module that was …

    …renamed to "base" when refactoring to a package...
    al-the-x committed Nov 22, 2011
  3. @al-the-x

    I wanted to use the "schema_file" option from "create" in "apply" so …

    …I moved it into the "base" module as "with_schema_file()". Opening "create" made me notice an omission in the "MIGRATION_TEMPLATE": I didn't fully qualify the function definition...! Oops.
    al-the-x committed Nov 22, 2011
  4. @al-the-x

    To be consistent with the other commands, I renamed the test... And a…

    …lso made it more verbose, which turns out to be quite helpful when debugging.
    al-the-x committed Nov 22, 2011
  5. @al-the-x
  6. @al-the-x
Commits on Nov 21, 2011
  1. @al-the-x

    Let's organize the code a little differently, with an eye towards dis…

    …tributing this as a cheeseshop package.
    al-the-x committed Nov 21, 2011
Commits on Oct 21, 2011
  1. @al-the-x

    Based on code review with the guys, some minor text changes... And no…

    … need to limit our "hash" field in "migrations"."history".
    al-the-x committed Oct 21, 2011
Commits on Oct 19, 2011
  1. @al-the-x

    I kept running this string of commands to test, so I thought I should…

    … add it, too. That also generates some migration files, which I wanted to ignore.
    al-the-x committed Oct 19, 2011
  2. @al-the-x

    In writing "migration-register", I realized that I needed some of the…

    … same functionality as in "migration-init", so I refactored to make that available. I thought that I'd need the "get_HASH()" method from "migrations-create", as well, and moved that into the parent class, but turns out not so.
    al-the-x committed Oct 19, 2011
  3. @al-the-x

    I thought it best to wrap all that SQL in a transaction, since it was…

    … breaking and all... And that helped in fixing the SQL. ;)
    al-the-x committed Oct 19, 2011
  4. @al-the-x

    Rather than making a dumb "psql" script, I opted to use the "migratio…

    …ns.Command" base class for "migrations-init" as well.
    al-the-x committed Oct 19, 2011
  5. @al-the-x
  6. @al-the-x

    Base class for migration commands that contains the reusable "Command…

    …" class and helper functions.
    al-the-x committed Oct 19, 2011
Commits on Oct 6, 2011
  1. @al-the-x

    Making the "MIGRATION_TEMPLATE" separate from "main()" means we can o…

    …verride it elsewhere, if we have to, and the code isn't broken up by a giant string constant.
    al-the-x committed Oct 6, 2011
  2. @al-the-x
Commits on Oct 4, 2011
  1. @al-the-x
Commits on Oct 3, 2011
  1. @al-the-x
  2. @al-the-x

    The basic structure that "migration-create" is expecting: a "schema.p…

    …g.sql" file that exists in version control and a "migrations" directory to put migrations in.
    al-the-x committed Oct 3, 2011
  3. @al-the-x

    Base commands that the migration assistant should understand: apply, …

    …create, init, and register. The "apply" command is just stubbed for the moment, "init" was the easiest (assuming pqsl is installed), and "create" is the most important immediately.
    al-the-x committed Oct 3, 2011