Yes, I'll try Plan A first(do the INSERT FROM first)
But mainly out of academic curiosity, if I were to start with a blank slate
as you say, I'd still need to import the existing data that is currently in
the non-inheritance table schema? So I guess I would just drop the
database, upgrade to
Thanks for the insight Mike. I guess the best way to go about that would be
to just call the raw insert sql statemen in the migration? like in
https://stackoverflow.com/questions/23206562/sqlalchemy-executing-raw-sql-with-parameter-bindings/23206636#23206636
Since this app is not in production
On 06/07/2017 04:44 PM, Michael wrote:
Hi all, I have a class called MediaChapter(Base), which I've refactored
into MediaBase(Base) and MediaChapter(MediaBase) When I run the
migration, I see:
|
psycopg2.IntegrityError:insert orupdate on table "mediachapter"violates
foreign key constraint
Hi all, I have a class called MediaChapter(Base), which I've refactored
into MediaBase(Base) and MediaChapter(MediaBase) When I run the migration,
I see:
psycopg2.IntegrityError: insert or update on table "mediachapter" violates
foreign key constraint "fk_mediachapter_id_mediabase"
DETAIL:
