I'm having a problem with indexes whose name is longer than
max_identifier_length and the comparisons during --autogenerate.
The index on the code/metadata side is being compared using its
auto-generated naming convention name, which doesn't take into account the
max_identifier_length since
I am integrating a new data source that provides schema data and versioning
in text files. The schema is comprised of several sub-schemas, and
overall, contains over 250+ tables. The data model is actually very good,
with lots of skinny tables/normalized properly.
The schema dialect for data
On 12/26/2015 11:44 PM, Krishnakant wrote:
> Hi,
> The subject says it all.
> I have classes inheriting the base and thus my tables are created using
> ORM.
> But I wish to use sql expression language for queries, particularly bulk
> selects for faster performance.
> So is this possible and how?
https://bitbucket.org/zzzeek/alembic/issues/351/autogen-with-constraint-names-that-were
is added
On 12/27/2015 07:57 PM, Mike Bayer wrote:
> that is kind of a bug for the time being. You'd need to name those
> constructs explicitly or exclude them using an include_object routine
> (see
>
On 12/27/2015 10:48 AM, Philip Martin wrote:
> I am integrating a new data source that provides schema data and
> versioning in text files. The schema is comprised of several
> sub-schemas, and overall, contains over 250+ tables. The data model is
> actually very good, with lots of skinny
On 27/12/2015 04:44, Krishnakant wrote:
Hi,
The subject says it all.
I have classes inheriting the base and thus my tables are created
using ORM.
But I wish to use sql expression language for queries, particularly
bulk selects for faster performance.
So is this possible and how?
Sure, you
