On Tue, Oct 31, 2017 at 12:18 AM, wrote:
> 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
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
On Mon, Oct 30, 2017 at 11:23 PM, wrote:
> 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 = Non
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
