summaryrefslogtreecommitdiff
path: root/test/zblog
Commit message (Collapse)AuthorAgeFilesLines
* - the zblog example is obsolete, the tests don't really test itMike Bayer2011-01-166-380/+0
| | | | | | and a key feature of its mapping (the deferred col outside of the select) doesn't work anyway. - add a token "deferred on selectable" test to test_mapper.
* - whitespace removal bonanzaMike Bayer2011-01-021-3/+3
|
* - move sqlalchemy.test to test.libMike Bayer2010-11-152-2/+2
|
* turn this test back to what it wasMike Bayer2010-09-121-2/+3
|
* - lazy loads for relationship attributes now useMike Bayer2010-09-121-5/+18
| | | | | | | | | | | | | | | | | | | | | the current state, not the "committed" state, of foreign and primary key attributes when issuing SQL, if a flush is not in process. Previously, only the database-committed state would be used. In particular, this would cause a many-to-one get()-on-lazyload operation to fail, as autoflush is not triggered on these loads when the attributes are determined and the "committed" state may not be available. [ticket:1910] - A new flag on relationship(), load_on_pending, allows the lazy loader to fire off on pending objects without a flush taking place, as well as a transient object that's been manually "attached" to the session. Note that this flag blocks attribute events from taking place when an object is loaded, so backrefs aren't available until after a flush. The flag is only intended for very specific use cases.
* - converted all lazy=True|False|None to 'select'|'joined'|'noload'Mike Bayer2010-03-241-9/+9
| | | | | - converted all eager to joined in examples - fixed beaker/advanced.py to reference RelationshipCache
* - The official name for the relation() function is nowMike Bayer2010-03-171-9/+9
| | | | | | relationship(), to eliminate confusion over the relational algebra term. relation() however will remain available in equal capacity for the foreseeable future. [ticket:1740]
* merge 0.6 series to trunk.Mike Bayer2009-08-064-14/+14
|
* - unit tests have been migrated from unittest to nose.Mike Bayer2009-06-104-41/+26
| | | | | See README.unittests for information on how to run the tests. [ticket:970]
* remove comparison/group by on TEXT columnsMike Bayer2009-01-191-1/+1
|
* fixed more save/clear callsMike Bayer2009-01-171-6/+6
|
* and try againMike Bayer2008-12-191-1/+1
|
* 2.4 doesnt have hashlib....Mike Bayer2008-12-191-1/+6
|
* merge the test/ directory from -r5438:5439 of py3k_warnings branch. this givesMike Bayer2008-12-181-1/+1
| | | | us a 2.5-frozen copy of unittest so we're insulated from unittest changes.
* merged -r5299:5438 of py3k warnings branch. this fixes some sqlite py2.6 ↵Mike Bayer2008-12-181-1/+1
| | | | | | | | testing issues, and also addresses a significant chunk of py3k deprecations. It's mainly expicit __hash__ methods. Additionally, most usage of sets/dicts to store columns uses util-based placeholder names.
* - Removed 2.3 set emulations/enhancements.Jason Kirtland2008-07-151-3/+3
| | | | (sets.Set-based collections & DB-API returns still work.)
* - updated the naming scheme of the base test classes in test/testlib/testing.py;Mike Bayer2008-02-111-1/+1
| | | | | tests extend from either TestBase or ORMTest, using additional mixins for special assertion methods as needed
* - Restored 2.3 compat. in lib/sqlalchemyJason Kirtland2008-01-191-0/+1
| | | | | | | - Part one of test suite fixes to run on 2.3 Lots of failures still around sets; sets.Set differs from __builtin__.set particularly in the binops. We depend on set extensively now and may need to provide a corrected sets.Set subclass on 2.3.
* - testbase is gone, replaced by testenvJason Kirtland2008-01-124-31/+27
| | | | | | - Importing testenv has no side effects- explicit functions provide similar behavior to the old immediate behavior of testbase - testing.db has the configured db - Fixed up the perf/* scripts
* test suite deprecation rampageJason Kirtland2008-01-092-51/+71
|
* - also added proxying of save_or_update to scoped sessions.Ants Aasma2007-10-311-0/+1
| | | | | - session.update() raises an error when updating an instance that is already in the session with a different identity - adjusted zoomarks lower limits so I can get a nice clean run
* Firebird dialect now uses SingletonThreadPool as its poolclass.Roger Demetrescu2007-10-071-3/+3
| | | | | | (this fixes all "unsuccessful metadata update\n object XXXXX is in use" test errors) Minor fixes in tests
* merging 0.4 branch to trunk. see CHANGES for details. 0.3 moves to ↵Mike Bayer2007-07-274-24/+22
| | | | maintenance branch in branches/rel_0_3.
* "alltests" runners call testbase.main(), which takes an optional suite,Mike Bayer2007-03-151-1/+1
| | | | so that exit code is propigated
* reorganizing classnames a bit, flagging "private" classes in the sql package,Mike Bayer2006-10-171-2/+2
| | | | | getting the generated docs to look a little nicer. fixes to extensions, sqlsoup etc. to be compatible with recent API tweaks
* - a fair amount of cleanup to the schema package, removal of ambiguousMike Bayer2006-10-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | methods, methods that are no longer needed. slightly more constrained useage, greater emphasis on explicitness. - table_iterator signature fixup, includes fix for [ticket:288] - the "primary_key" attribute of Table and other selectables becomes a setlike ColumnCollection object; is no longer ordered or numerically indexed. a comparison clause between two pks that are derived from the same underlying tables (i.e. such as two Alias objects) can be generated via table1.primary_key==table2.primary_key - append_item() methods removed from Table and Column; preferably construct Table/Column/related objects inline, but if needed use append_column(), append_foreign_key(), append_constraint(), etc. - table.create() no longer returns the Table object, instead has no return value. the usual case is that tables are created via metadata, which is preferable since it will handle table dependencies. - added UniqueConstraint (goes at Table level), CheckConstraint (goes at Table or Column level) fixes [ticket:217] - index=False/unique=True on Column now creates a UniqueConstraint, index=True/unique=False creates a plain Index, index=True/unique=True on Column creates a unique Index. 'index' and 'unique' keyword arguments to column are now boolean only; for explcit names and groupings of indexes or unique constraints, use the UniqueConstraint/Index constructs explicitly. - relationship of Metadata/Table/SchemaGenerator/Dropper has been improved so that the schemavisitor receives the metadata object for greater control over groupings of creates/drops. - added "use_alter" argument to ForeignKey, ForeignKeyConstraint, but it doesnt do anything yet. will utilize new generator/dropper behavior to implement.
* - logging is now implemented via standard python "logging" module.Mike Bayer2006-09-241-1/+1
| | | | | | | | | | | | | "echo" keyword parameters are still functional but set/unset log levels for their respective classes/instances. all logging can be controlled directly through the Python API by setting INFO and DEBUG levels for loggers in the "sqlalchemy" namespace. class-level logging is under "sqlalchemy.<module>.<classname>", instance-level logging under "sqlalchemy.<module>.<classname>.<hexid>". Test suite includes "--log-info" and "--log-debug" arguments which work independently of --verbose/--quiet. Logging added to orm to allow tracking of mapper configurations, row iteration fixes [ticket:229] [ticket:79]
* forgot the tearDown step....Mike Bayer2006-09-071-0/+1
|
* - added basic 'zblog' test suiteMike Bayer2006-09-057-0/+359
- better error message for mapper orphan detect
View Lorry Controller Status