Files
sqlalchemy/doc/build/core
Mike Bayer fd2ecb5f87 Remove "subclass existing types" use case
Thanks to :ref:`change_3981`, we no longer need to rely on recipes that
subclass dialect-specific types directly, :class:`.TypeDecorator` can now
handle all cases.   Additionally, the above change made it slightly less
likely that a direct subclass of a base SQLAlchemy type would work as
expected, which could be misleading.  Documentation has been updated to use
:class:`.TypeDecorator` for these examples including the PostgreSQL
"ArrayOfEnum" example datatype and direct support for the "subclass a type
directly" has been removed.

Fixes: #4580
Change-Id: I866f246cccc736ea618dc965ab3604762f7a52fe
2019-03-29 09:46:55 -04:00
..
2014-12-27 16:22:41 -05:00
2019-01-25 14:56:50 -05:00
2019-01-18 01:02:07 -05:00
2017-12-22 12:35:30 -05:00
2014-12-27 16:54:32 -05:00
2019-03-05 19:42:41 -05:00
2019-01-25 14:56:50 -05:00
2014-12-27 16:22:41 -05:00
2014-12-27 16:22:41 -05:00