Mike Bayer f146f19d4b Unify NO_VALUE and NEVER_SET ...

There's no real difference between these two constants
except they are used in different places and therefore allow
various codepaths to work largely by accident.   These
codepaths should be explicit.   Assign NO_VALUE and NEVER_SET
to the same constant and work towards having just one constant
for "we have no value to return right now".

Fixes: #4696
Change-Id: I7c324967952c1886bf202074d627323a2ad013cc

2019-05-24 18:48:01 -04:00

..

aaa_profiling

Add autoincrement to test_orm AnnotatedOverheadTest for Oracle

2019-05-11 11:40:56 -04:00

base

Add test to as_interface when no cls or methods

2019-02-21 14:22:48 -05:00

dialect

Implement new ClauseElement role and coercion system

2019-05-18 17:46:10 -04:00

engine

Move initialize do_rollback() outside of the dialect

2019-05-09 21:50:59 -04:00

ext

Add QueryableAttribute._impl_uses_objects accessor for AssociationProxy

2019-05-19 13:58:01 -04:00

orm

Unify NO_VALUE and NEVER_SET

2019-05-24 18:48:01 -04:00

perf

Post black reformatting

2019-01-06 18:23:11 -05:00

sql

Implement new ClauseElement role and coercion system

2019-05-18 17:46:10 -04:00

__init__.py

- the NoseSQLAlchemyPlugin has been moved to a

2010-10-17 15:23:14 -04:00

binary_data_one.dat

fixed binary types test to use two binary files specifically for testing, instead of

2006-10-30 01:29:43 +00:00

binary_data_two.dat

fixed binary types test to use two binary files specifically for testing, instead of

2006-10-30 01:29:43 +00:00

conftest.py

Post black reformatting

2019-01-06 18:23:11 -05:00

profiles.txt

Implement new ClauseElement role and coercion system

2019-05-18 17:46:10 -04:00

requirements.py

Open up mysql CHECK constraint detection to include new versions

2019-05-04 23:04:06 -06:00