Locations don't appear to work.

[ThePixelDeveloper]

I'm having trouble getting the locations feature to work properly.

I only want to run migrations under a directory called nolimits. I've tried.

• ./minion db:migrate --dry-run --versions=nolimits:TRUE
• ./minion db:migrate --dry-run --locations=nolimits --versions=TRUE

but both of those commands are outputting:

##########################
# Begin Location: minion #
##########################

# Begin 20110110093709

CREATE TABLE `test_minion_migrations` (
  `timestamp` varchar(14) NOT NULL,
  `description` varchar(100) NOT NULL,
  `location` varchar(100) NOT NULL,
  `applied` tinyint(1) DEFAULT '0',
  PRIMARY KEY (`timestamp`,`location`),
  UNIQUE KEY `MIGRATION_ID` (`timestamp`,`description`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;;

# End 20110110093709

########################
# End Location: minion #
########################

Am I missing something or is the feature broken?

[ThePixelDeveloper]

Ok.

The problem was I had not created the nolimits directory, maybe it'd be nice to show a warning instead of migrations which don't apply.

The next problem was only

./minion db:migrate --dry-run --locations=nolimits --versions=TRUE

displayed the correct migrations (with the directory created), where as:

./minion db:migrate --dry-run --versions=nolimits:TRUE

would still give me the incorrect output.

[BRMatt]

Now throws an exception if a group doesn't exist, just need to prettify the output.

[bobeagan]

Is this ticket still relevant? Can you reproduce this problem using the new option configuration?

[BRMatt]

Going to close this, please reopen if problem exists / resurfaces