Re: Running Migrations Simulataneously

On Wed, Apr 27, 2016 at 11:31 PM, Mike Bayer wrote: > Yes, you can implement that inside your env.py if you wanted.All the > other processes would wait and once inside the lock they all need to > re-check the version.Not something alembic would include, though.

Re: Running Migrations Simulataneously

Yes, you can implement that inside your env.py if you wanted.All the other processes would wait and once inside the lock they all need to re-check the version.Not something alembic would include, though. On Tuesday, April 26, 2016, Amit Saha wrote: > On Wed, Apr

Re: Running Migrations Simulataneously

On 04/26/2016 01:22 AM, Amit Saha wrote: On Tue, Apr 26, 2016 at 12:33 PM, Mike Bayer wrote: On 04/25/2016 08:30 PM, Amit Saha wrote: Hi all, In my scenario, DB migrations (via alembic) will be run as part of the app deployment and multiple app deployments will

Re: Running Migrations Simulataneously

On Tue, Apr 26, 2016 at 12:33 PM, Mike Bayer wrote: > > > On 04/25/2016 08:30 PM, Amit Saha wrote: >> >> Hi all, >> >> In my scenario, DB migrations (via alembic) will be run as part of the >> app deployment and multiple app deployments will happen near >> simultaneously

Re: Running Migrations Simulataneously

On 04/25/2016 08:30 PM, Amit Saha wrote: Hi all, In my scenario, DB migrations (via alembic) will be run as part of the app deployment and multiple app deployments will happen near simultaneously (multiple EC2 instances talking to the same MySQL DB). Let's, for simplicity's sake assume two

Running Migrations Simulataneously

Hi all, In my scenario, DB migrations (via alembic) will be run as part of the app deployment and multiple app deployments will happen near simultaneously (multiple EC2 instances talking to the same MySQL DB). Let's, for simplicity's sake assume two instances: Instance #1: Alembic sees