summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* editmulti_db_testsMike Bayer2014-03-031-2/+3
|
* - documentation and changelogMike Bayer2014-03-035-79/+199
|
* - fix oracle failures here due to mis-orderingMike Bayer2014-03-032-1/+2
|
* hey we can use unittest.SkipTestMike Bayer2014-03-033-18/+8
|
* figure out module location a bit betterMike Bayer2014-03-032-6/+3
|
* - transfer to non-unittest usage. a little more tricky.Mike Bayer2014-03-034-32/+44
|
* - integrate into setupMike Bayer2014-03-031-2/+2
|
* cleanupMike Bayer2014-03-031-7/+1
|
* framework agnostic coverage flagMike Bayer2014-03-034-2/+9
|
* - go through a more complex process here to work around a dict reordering ↵Mike Bayer2014-03-036-14/+43
| | | | issue in pytest
* mark all suite tests as __multiple__Mike Bayer2014-03-037-0/+27
|
* - fix failure casesMike Bayer2014-03-034-46/+61
| | | | - get dropfirst to work around missing schemas
* test branchingMike Bayer2014-03-034-40/+39
|
* more test fixes, removing old deprecated tests that haven't been running...Mike Bayer2014-03-023-52/+1
|
* we dont need to trick the importer! wowMike Bayer2014-03-022-16/+2
|
* updatesMike Bayer2014-03-026-3/+29
|
* that seems to workMike Bayer2014-03-021-3/+3
|
* - working through this..Mike Bayer2014-03-026-36/+93
|
* - break out all the test extensions from being nose-specific and beginMike Bayer2014-03-027-442/+1086
| | | | getting them all compatible with py.test as well
* save some various scratch work for trying to make __multiple__ workMike Bayer2014-03-022-3/+87
|
* - remove the "utf8_engine" concept; current MySQL + drivers don't haveMike Bayer2014-03-028-92/+58
| | | | | an issue with utf8, and this should be part of the testing URL in any case. if we observe failures on some drivers/etc. this can become a "requires"
* - this test is crap, remove itMike Bayer2014-03-021-26/+0
|
* - cleanup, solidify ConfigMike Bayer2014-03-027-54/+92
|
* - get everything working again test-wise...Mike Bayer2014-03-022-4/+8
|
* - remove lots of old and unused nose optionsMike Bayer2014-03-019-209/+209
| | | | | | | | | | - alter the plugin/requirements system to support multiple --db/--dburi options. The first option serves as the "default" database, and the subsequent ones serve as "available" databases. the requirement rules at the *class level only* now search among the "available" databases in order to run per-database test suites at once. rationale is to support using the test plugin system under Alembic as well, which already takes advantage of multiple database tests.
* - add new tests for individual type reflectionMike Bayer2014-03-011-0/+46
|
* use view_column requirement hereMike Bayer2014-02-281-3/+3
|
* - dont create a self-ref FK if test suite marked as not supporting self refMike Bayer2014-02-282-13/+27
| | | | | - break out reflection of views to support view column reflection separately from view definition
* fix typosMike Bayer2014-02-282-2/+2
|
* add a migration for this oneMike Bayer2014-02-281-3/+36
|
* - Added a new option to :paramref:`.relationship.innerjoin` which isMike Bayer2014-02-285-29/+259
| | | | | | | | | | | to specify the string ``"nested"``. When set to ``"nested"`` as opposed to ``True``, the "chaining" of joins will parenthesize the inner join on the right side of an existing outer join, instead of chaining as a string of outer joins. This possibly should have been the default behavior when 0.9 was released, as we introduced the feature of right-nested joins in the ORM, however we are keeping it as a non-default for now to avoid further surprises. fixes #2976
* - Fixed bug in :func:`.tuple_` construct where the "type" of essentiallyMike Bayer2014-02-273-6/+41
| | | | | | | | | | | the first SQL expression would be applied as the "comparison type" to a compared tuple value; this has the effect in some cases of an inappropriate "type coersion" occurring, such as when a tuple that has a mix of String and Binary values improperly coerces target values to Binary even though that's not what they are on the left side. :func:`.tuple_` now expects heterogeneous types within its list of values. fixes #2977
* restore the contracts of update/extend to the degree that the same column ↵Mike Bayer2014-02-272-3/+35
| | | | | | identity isn't appended to the list. reflection makes use of this.
* - Fixed a regression in association proxy caused by :ticket:`2810` whichMike Bayer2014-02-273-6/+45
| | | | | | | | | caused a user-provided "getter" to no longer receive values of ``None`` when fetching scalar values from a target that is non-present. The check for None introduced by this change is now moved into the default getter, so a user-provided getter will also again receive values of None. re: #2810
* - Removed stale names from ``sqlalchemy.orm.interfaces.__all__`` andMike Bayer2014-02-262-4/+16
| | | | | | refreshed with current names, so that an ``import *`` from this module again works. fixes #2975
* - Adjusted the logic which applies names to the .c collection whenMike Bayer2014-02-264-9/+29
| | | | | | | | | a no-name :class:`.BindParameter` is received, e.g. via :func:`.sql.literal` or similar; the "key" of the bind param is used as the key within .c. rather than the rendered name. Since these binds have "anonymous" names in any case, this allows individual bound parameters to have their own name within a selectable if they are otherwise unlabeled. fixes #2974
* - Some changes to how the :attr:`.FromClause.c` collection behavesMike Bayer2014-02-265-33/+269
| | | | | | | | | | | | | | | | | | | | | | | when presented with duplicate columns. The behavior of emitting a warning and replacing the old column with the same name still remains to some degree; the replacement in particular is to maintain backwards compatibility. However, the replaced column still remains associated with the ``c`` collection now in a collection ``._all_columns``, which is used by constructs such as aliases and unions, to deal with the set of columns in ``c`` more towards what is actually in the list of columns rather than the unique set of key names. This helps with situations where SELECT statements with same-named columns are used in unions and such, so that the union can match the columns up positionally and also there's some chance of :meth:`.FromClause.corresponding_column` still being usable here (it can now return a column that is only in selectable.c._all_columns and not otherwise named). The new collection is underscored as we still need to decide where this list might end up. Theoretically it would become the result of iter(selectable.c), however this would mean that the length of the iteration would no longer match the length of keys(), and that behavior needs to be checked out. fixes #2974 - add a bunch more tests for ColumnCollection
* - Fixed issue in new :meth:`.TextClause.columns` method where the orderingMike Bayer2014-02-264-7/+54
| | | | | | of columns given positionally would not be preserved. This could have potential impact in positional situations such as applying the resulting :class:`.TextAsFrom` object to a union.
* - use MutableMapping to make this more succinct, completeMike Bayer2014-02-261-47/+35
|
* docsMike Bayer2014-02-254-19/+45
|
* - The new dialect-level keyword argument system for schema-levelMike Bayer2014-02-255-14/+320
| | | | | | | | | constructs has been enhanced in order to assist with existing schemes that rely upon addition of ad-hoc keyword arguments to constructs. - To suit the use case of allowing custom arguments at construction time, the :meth:`.DialectKWArgs.argument_for` method now allows this registration. fixes #2962
* - Fixed bug where events set to listen at the classMike Bayer2014-02-253-6/+44
| | | | | | | | level (e.g. on the :class:`.Mapper` or :class:`.ClassManager` level, as opposed to on an individual mapped class, and also on :class:`.Connection`) that also made use of internal argument conversion (which is most within those categories) would fail to be removable. fixes #2973
* - we're testing a query here with non-standard aliasing which fails on PG ↵Mike Bayer2014-02-241-0/+6
| | | | | | | and MySQL. Leave this test in place as its ultimately a SQLite use case, but only test on SQLite. We perhaps should add another test case that works on all platforms.
* - Fixed regression from 0.8 where using an option likeMike Bayer2014-02-243-0/+25
| | | | | | | :func:`.orm.lazyload` with the "wildcard" expression, e.g. ``"*"``, would raise an assertion error in the case where the query didn't contain any actual entities. This assertion is meant for other cases and was catching this one inadvertently.
* - Fixed bug in the versioned_history example where column-level INSERTMike Bayer2014-02-243-5/+44
| | | | defaults would prevent history values of NULL from being written.
* more detail, what actually loads, etc.Mike Bayer2014-02-231-3/+66
|
* -rewrite expire/refresh sectionMike Bayer2014-02-233-63/+192
|
* no more wheels until they have a pointMike Bayer2014-02-221-2/+0
| | | | fixes #2970
* - More fixes to SQLite "join rewriting"; the fix from :ticket:`2967`Mike Bayer2014-02-205-15/+112
| | | | | | | | | | | | | | implemented right before the release of 0.9.3 affected the case where a UNION contained nested joins in it. "Join rewriting" is a feature with a wide range of possibilities and is the first intricate "SQL rewriting" feature we've introduced in years, so we're sort of going through a lot of iterations with it (not unlike eager loading back in the 0.2/0.3 series, polymorphic loading in 0.4/0.5). We should be there soon so thanks for bearing with us :). fixes #2969 re: #2967 - solve the issue of join rewriting inspecting various types of from objects without using isinstance(), by adding some new underscored inspection flags to the FromClause hierarchy.
* fix typorel_0_9_3Mike Bayer2014-02-191-1/+1
|
View Lorry Controller Status