Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Aug 8, 2015
  1. Move write_plan to TargetConfigCommand.

    authored
    So that the other commands can use it.
Commits on Aug 7, 2015
  1. Add config_target to TargetConfigCommand.

    authored
    And use it in the init command. This tries to create the best possible target
    object based on all the properties passed to the command.
  2. Add all other --set options to init.

    authored
    Require the new `property_keys` method in the class that applies the
    TargetConfigCommand role, and use it to enforce what keys are allowed. Then
    just use the properties thus specified when writing the configuration file.
    
    New properties include engine, top_dir, client, plan_file, and registry. Each
    will get the value passed via the core option, though use of --set is
    preferred. Also added target, which will cause a target section to be added to
    the config if the target is not a URI. Target, registry, and client are all
    added to the engine section.
    
    The init command also injects the engine into the core --engine option, if
    it's not specified, since Target looks there to load the proper engine and
    create the proper URI. We need that for defaults. It's a bit hinky, but it
    works.
    
    The upshot is that the interface is now almost identical to that of the engine
    command.
    
    And simplify how things are written to the configuration file.
Commits on Aug 6, 2015
  1. Use --set in the init command.

    authored
    Instead of --dir. Also set extension this way, removing --extension. This
    brings it closer to the interface of the engine and target commands.
  2. Replace engine set-* actions with alter action.

    authored
    Will make it easier to modify engine properties, including many at once. The
    set-* actions are now deprecated, and emit a warning, except for the
    `set-reworked*` actions, which are simply removed (never released).
Commits on Aug 5, 2015
  1. Teach engine command about reworked directories.

    authored
    And reformat the output of `show` to be a bit less flat, so hopefully
    easier to read.
    
    I'm not entirely happy with the proliferation of `set-` actions in this
    command. I originally borrowed it from `git remote`, but starting to think it
    might have been better to just use a --set option like the `add` command uses.
    I still might go back to that...
  2. Update sqitch-configuration.

    authored
Commits on Aug 4, 2015
  1. Replace multiple directory options with --dir.

    authored
    Will be a better fit for the engine and target commands, and is saner if more
    directories get added in the future.
  2. Move script-specific references from init command code.

    authored
    Encapsulate that functionality as methods on ScriptConfigCommand, instead.
  3. Move script option handling to a role.

    authored
    The new role, App::Sqitch::Role::ScriptConfigCommand, encapsulates those
    options and attributes, previously implemented in the init comamnd. This role
    will alo be used for the other script configuration commands, engine and
    target.
  4. Add directory options to the init command.

    authored
    Also --extension. The equivalent core options will be deprecated.
Commits on Aug 3, 2015
  1. Remove reworked options.

    authored
    I don't think the need to be core options; they're rarely used. They're fine
    as configuration options, and will be added to init, engine, and target
    commands as appropriate.
  2. Teach init about reworked directories.

    authored
    And stop writing out commented values for `deploy_dir`, `revert_dir`, or
    `verify_dir` settings. I think these settings are not commonly used, and it
    would start to get crowded if we also added their "reworked" variants, which
    will be used still less.
  3. Test bundling of reworked change scripts.

    authored
    When they are not in the default directory. Requires the creation of such
    scripts, so a change to a test plan, which then requires changes to a few
    other tests that use the same plan.
  4. Bundle reworked scripts.

    authored
    Switch to a hash of destination directories, and look up the proper paths
    in that hash. Should be a bit more efficient, too.
Commits on Aug 2, 2015
  1. Wordsmithing.

    authored
  2. Teach Change to use reworked_* directories.

    authored
    For reworked changes only, of course.
  3. Add --reworked* options.

    authored
    These specify directories into which to put reworked scripts.
Commits on Aug 1, 2015
  1. @bokutin

    tiny doc fix

    bokutin authored
Commits on Jul 31, 2015
  1. Add --set support to the MySQL engine.

    authored
    Many thanks to Chris Bandy for the pointer demonstrating how to do it.
    Closes #236.
Commits on Jul 22, 2015
Commits on Jul 20, 2015
  1. @olshevskiy87
Commits on Jul 8, 2015
  1. Let Oracle deploy > 1000 changes.

    authored
    Oracle has a configured limit on the number of items that may appear in an
    IN() clause. So break it up into mutliple IN() clauses of no more than 250
    items each. Oracle allows 1000 by default, but it's configurable, so let's
    just try to play it safe by assuming it could be as low as 200.
Commits on Jul 6, 2015
  1. Apparently I can't count.

    authored
  2. Work around missing mysql_* attributes.

    authored
    When using a version of DBI prior to 1.63. Resolves #235.
Something went wrong with that request. Please try again.