sqlalchemy-bot

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** Issue #471 was marked as a duplicate of this issue.

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** Issue #484 was marked as a duplicate of this issue.

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** Issue #488 was marked as a duplicate of this issue.

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * removed labels: **autogenerate - rendering** * added labels: **postgresql typing issues**

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **title** from "Autogenerate doesn't correctly handle enums" to "Autogenerate doesn't correctly handle postgresql e"

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** Hi - I would assume this is arising because you are using the automated naming convention feature. SQLAlchemy itself should not be generating too-long names because...

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** or perhaps the truncation isn't taking effect on the SQLAlchemy side for names. This would be a SQLAlchemy bug. If you can please provide specifics we...

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** here's that SQLAlchemy issue already there: https://bitbucket.org/zzzeek/sqlalchemy/issues/3989/warn-error-for-too-long-naming-convention

**Changes by Danny Milosavljevic:** * edited description

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **title** from "Index name auto-truncation done in postgres but no" to "if/when SQLAlchemy provides truncation for naming "