On Fri, Jan 8, 2016 at 8:09 PM Mike Bayer <mike...@zzzcomputing.com> wrote:
> the general idea here is to make your own Alembic command runner, create > a Config dynamically and then invoke the alembic commands via > alembic.command.foo() from that. > > Mike, Thanks for the answer. I'm going to create an alembic runner just the one that gets installed but I'm going to replace CommandLine class to send config_args parameter to Config class replacing a single variable in my alembic.ini file. That variable will have all the directories in where migrations will live and will be generated by reading the configuration of the project. This approach leaves me with all the functionality that alembic currently has, and the same interface, errors and parameters. I think is pretty simple and transparent to the user. Martín -- Martín +54 911 5112 9448 Skype: kyheo_ -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
