sqlalchemy-bot

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **title** from "incorrect migration script generated if schema con" to "take use_alter=True other FK constraint rules into"

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

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * set **milestone** to "fasttrack"

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **milestone** from "fasttrack" to "tier 1"

**Changes by Michael Bayer ([@zzzeek](https://github.com/zzzeek)):** * changed **title** from "take use_alter=True other FK constraint rules into" to "take use_alter=True other FK / foreign key / forei"

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** #67 is probably not a great built-in solution to this issue, as that solution does not accommodate for the fact that ENUM has different implementations on...

**Leonardo ([@leotada](https://github.com/leotada)) wrote:** Why does not check if the type exists and tries to create if not, or alter if the name is the same. https://stackoverflow.com/questions/7624919/check-if-a-user-defined-type-already-exists-in-postgresql

**Michael Bayer ([@zzzeek](https://github.com/zzzeek)) wrote:** @leotada sure. The work is, "works with the generic Enum as well as PG ENUM, doesn't interfere with other backends, has plenty of functional tests".

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

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