Mike Bayer 8a7fdd4e5c - A quasi-regression where apparently in 0.8 you can set a class-level ...

attribute on declarative to simply refer directly to an :class:`.InstrumentedAttribute`
on a superclass or on the class itself, and it
acts more or less like a synonym; in 0.9, this fails to set up enough
bookkeeping to keep up with the more liberalized backref logic
from 🎫`2789`.  Even though this use case was never directly
considered, it is now detected by declarative at the "setattr()" level
as well as when setting up a subclass, and the mirrored/renamed attribute
is now set up as a :func:`.synonym` instead. [ticket:2900]

2014-01-02 18:51:49 -05:00

..

aaa_profiling

- the wrapped memoized_property here was not working, as the attribute name

2013-11-26 23:24:13 -05:00

base

- Improvements to the system by which SQL types generate within

2013-12-18 18:26:15 -05:00

dialect

- support addition of fails_if()/only_on(), just wraps the decorators

2014-01-02 14:23:14 -05:00

engine

- The :func:.engine_from_config function has been improved so that

2013-12-07 18:38:15 -05:00

ext

- A quasi-regression where apparently in 0.8 you can set a class-level

2014-01-02 18:51:49 -05:00

orm

- Fixed regression where we apparently still create an implicit

2014-01-02 18:26:32 -05:00

perf

- the wrapped memoized_property here was not working, as the attribute name

2013-11-26 23:24:13 -05:00

sql

a few oracle test failures

2013-12-28 18:24:43 -05:00

__init__.py

…

binary_data_one.dat

…

binary_data_two.dat

…

profiles.txt

- the wrapped memoized_property here was not working, as the attribute name

2013-11-26 23:24:13 -05:00

requirements.py

- support addition of fails_if()/only_on(), just wraps the decorators

2014-01-02 14:23:14 -05:00