On 09/22/2016 01:29 PM, Chris Withers wrote:
On 22/09/2016 14:55, Mike Bayer wrote:
On 09/22/2016 07:30 AM, Chris Withers wrote:
How do you control the order in which columns are added to a
multi-column primary key when using the declarative primary_key=True
syntax?
How about when one of
On 22/09/2016 14:55, Mike Bayer wrote:
On 09/22/2016 07:30 AM, Chris Withers wrote:
How do you control the order in which columns are added to a
multi-column primary key when using the declarative primary_key=True
syntax?
How about when one of those columns comes from a mixin?
without
On 09/22/2016 10:21 AM, Seth P wrote:
The documentation for DateTime,
http://docs.sqlalchemy.org/en/latest/core/type_basics.html?highlight=datetime#sqlalchemy.types.DateTime,
states
Parameters:*timezone* – boolean. If True, and supported by the backend,
will produce ‘TIMESTAMP WITH TIMEZONE’.
The documentation for DateTime,
http://docs.sqlalchemy.org/en/latest/core/type_basics.html?highlight=datetime#sqlalchemy.types.DateTime,
states
Parameters:*timezone* – boolean. If True, and supported by the backend,
will produce ‘TIMESTAMP WITH TIMEZONE’. For backends that don’t support
On 09/22/2016 07:30 AM, Chris Withers wrote:
Hi All,
How do you control the order in which columns are added to a
multi-column primary key when using the declarative primary_key=True syntax?
How about when one of those columns comes from a mixin?
without mixins, the columns are processed in
On 09/22/2016 02:51 AM, Tom Walter wrote:
I work in a team of people collaborating on database development and
we'd like to start version controlling and deploy our changes with Alembic.
I was wondering though if there is a way to generate the DDL for the
current state of the whole schema as
Hi All,
How do you control the order in which columns are added to a
multi-column primary key when using the declarative primary_key=True syntax?
How about when one of those columns comes from a mixin?
Context is in the mail below, any help gratefully received!
Chris
Forwarded
I work in a team of people collaborating on database development and we'd
like to start version controlling and deploy our changes with Alembic.
I was wondering though if there is a way to generate the DDL for the
current state of the whole schema as of a given revision... something like
the