Re: [sqlalchemy] persisted enum value from PEP-435 enum

quot;validate_strings", impl.validate_strings) > +kw.setdefault("values_callable", impl.values_callable) > return cls(**kw) > > def _setup_for_values(self, values, objects, kw): > > On Tue, Dec 26, 2017 at 8:07 PM, Jon Snyder <snyder@gmail.c

Re: [sqlalchemy] persisted enum value from PEP-435 enum

a breakpoint into Enum._enum_init, I see the correct values being populated from my function. But I'm clearly missing a step here. Jon On Tue, Dec 26, 2017 at 1:38 PM, Mike Bayer <mike...@zzzcomputing.com> wrote: > On Tue, Dec 26, 2017 at 12:49 PM, Jon Snyder <snyder@gmail.com&

Re: [sqlalchemy] persisted enum value from PEP-435 enum

4, 2017 at 1:56 PM, Mike Bayer <mike...@zzzcomputing.com> wrote: > On Mon, Dec 4, 2017 at 12:35 PM, Jon Snyder <snyder@gmail.com> wrote: > > Hi, > > > > The documentation and code is quite clear that it's the name, not the > value, > > of

[sqlalchemy] persisted enum value from PEP-435 enum

Hi, The documentation and code is quite clear that it's the name, not the value, of a PEP-435 compliant enum that is persisted to the database. My use case is that existing enums already in the db are using strings that are not