I checked the db post failed migration for bacnet_object. The
Entityproperty table no longer has that column. Plus the migration upward
from base to head works fine.
On Tuesday, October 31, 2017 at 9:27:59 AM UTC+5:30, Mike Bayer wrote:
>
> On Mon, Oct 30, 2017 at 11:23 PM, >
> wrote:
> > I ha
The EntityProperty table was created by application itself from a time
earlier to the introduction of alembic for the migrations. So should I
create the EntityProperty table in the migration script itself? If so then
how the models connect. The one sitting in the application and the one in
the
I have 2 migration scripts.
The first 1 (base) is this
from models import EntityProperty
from contextlib import contextmanager
# revision identifiers, used by Alembic.
revision = 'ecbde8fa83e3'
down_revision = None
branch_labels = None
depends_on = None
from alembic import op # noqa
impor
ght about doing it in alembic and not done it because
that may not be the best idea? Just trying to understand.
>
>
> On Tuesday, April 26, 2016, Amit Saha wrote:
>>
>> On Wed, Apr 27, 2016 at 12:37 AM, Mike Bayer
>> wrote:
>> >
>> >
>> > On 0
On Wed, Apr 27, 2016 at 12:37 AM, Mike Bayer wrote:
>
>
> 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:
>>>
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
&g
a read/write lock on
alembic_version table for the entire migration? (And hence instance #2
never will need to run the migration since when it reads alembic_version,
the DB already has the migrated schema).
Thanks for your insights.
Best Wishes,
Amit.
--
You received this message because y
