| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
- add the other versioning examples from the wiki
- modernize the dictlike examples
|
|
|
|
|
|
|
|
|
| |
viewcode extension
to allow ad-hoc display of the source of any file, as well as a "directory listing" structure.
- reorganize examples/ to take advantage of new extension. in particular, keep moving all
the descriptive text for files etc. into module docstrings, taking more advantage of
self-documentation.
|
| |
|
|
|
|
|
|
| |
joined inheritance schemes more than one level deep.
- don't need to use _lib.py here anymore now that these features are in
sqlalchemy.testing
|
|
|
|
| |
- clean up these tests to not use globals so much, close out the session
|
| |
|
|
|
|
| |
follow up to https://bitbucket.org/zzzeek/sqlalchemy/pull-request/2
|
|
|
|
| |
The code that determines whether an object in a relation has been added/removed does not take into account that that relation may be a backref. If the relation is a backref, then nothing on the current table is changing, and therefore no history entry should be created.
|
|
|
|
| |
- went through examples/ and cleaned out excess list() calls
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
a bit to use a declarative mixin as well
as an event listener, instead of a metaclass +
SessionExtension. [ticket:2313]
|
|
|
|
|
|
| |
the "unique" flag was not removed from a
single-table-inheritance subclass which
generates columns to put up onto the base.
|
|
|
|
|
|
|
|
|
|
|
| |
to not rely upon SQLAlchemy test libs,
nosetests must be run from within
examples/versioning to get around setup.cfg
breaking it.
- Tweak to examples/versioning to pick the
correct foreign key in a multi-level
inheritance situation.
|
|
|
|
|
|
|
| |
classes to a new test.lib.fixtures module
- move testing.TestBase to test.lib.fixtures
- massive search and replace
|
| |
|
| |
|
| |
|
|
|
|
|
| |
if versioning on a col that was formerly
NULL.
|
|
|
|
|
|
|
|
| |
by the versioning example is deprecated;
now use mapper.get_property_by_column() which
will remain the public method for this.
- turned TODO in the history example into an assertion
with a descriptive reason
|
|
|
|
|
|
| |
when copying columns, so that the versioning
table handles multiple rows with repeating values.
[ticket:1887]
|
| |
|
|
- added READMEs to all examples in each __init__.py and added to sphinx documentation
- added versioning example
- removed vertical/vertical.py, the dictlikes are more straightforward
|