Hi,
I have a use case where I have two databases, each of which provides a
subset of my models. I have two seperate __abstract__ base classes (each
with its own metadata) that each model inherits from to determine on which
database they belong. To manage separate migrations on each, I will most
6 PM UTC+1, Michael Bayer wrote:
>
>
> On Jan 14, 2014, at 4:56 PM, Dimitris Theodorou
> >
> wrote:
>
> Tried your approach but I can't get past the inspector wall.
>
> I set the search_path using connection.execute(), then call
> context.configure(connection,
>
bject as it is more
> portable just to have it set up on the connection.
>
>
> On Jan 14, 2014, at 9:16 AM, Dimitris Theodorou
> >
> wrote:
>
> My progress so far has been to configure my Metadata.schema before
> importing my Declarative objects (which is going to associate A
the created version script, I want to add all modifications in 1 script.
On Tuesday, January 14, 2014 3:09:55 PM UTC+1, Dimitris Theodorou wrote:
>
> Hi,
>
> Also posted this question at
> http://stackoverflow.com/questions/21109218/alembic-support-for-multiple-postgres-schemas,
Hi,
Also posted this question at
http://stackoverflow.com/questions/21109218/alembic-support-for-multiple-postgres-schemas,
not sure what the best place to continue is.
My problem is the following:
I have one SQL alchemy model with no schema specifications. In my database
though I duplicate
