-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Bayer ha scritto:
> Manlio Perillo wrote:
>> PoolListener is rather low level; if I use them I need to know in
>> advance the secondary databases to attach.
>
> What precisely is the use case for an application that will use a database
> X, wi
Manlio Perillo wrote:
>
> PoolListener is rather low level; if I use them I need to know in
> advance the secondary databases to attach.
What precisely is the use case for an application that will use a database
X, will be using remote schemas P, Q, and R, but its unreasonable for
those schemas P,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Bayer ha scritto:
> Manlio Perillo wrote:
>> When writing this code I found some problems with SQLAlchemy:
>>
>> 1) There is no support for SQL Schema at all.
>>
>>It is ok, for me, if there is no direct support for SQL Schema in
>>SQLA
Manlio Perillo wrote:
> When writing this code I found some problems with SQLAlchemy:
>
> 1) There is no support for SQL Schema at all.
>
>It is ok, for me, if there is no direct support for SQL Schema in
>SQLAlchemy, but this is a standard feature, so SQLALchemy dialects
>should:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Bayer ha scritto:
> Manlio Perillo wrote:
> Hi.
>
> I would like to use SQL schemas in my projects, however support in
> SQLAlchemy is quite poor.
>
> What I want to do is to create a custom MetaData object, that allows me
> to specify the de
Manlio Perillo wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi.
>
> I would like to use SQL schemas in my projects, however support in
> SQLAlchemy is quite poor.
>
> What I want to do is to create a custom MetaData object, that allows me
> to specify the default schema name to use.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I would like to use SQL schemas in my projects, however support in
SQLAlchemy is quite poor.
What I want to do is to create a custom MetaData object, that allows me
to specify the default schema name to use.
All tables bound to that meta data, w
