summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* - determine the root cause of the mysqlconnector issue, reportMike Bayer2014-07-101-5/+4
| | | | it and move on
* - mark tests failing for mysqlconnector, oursqlMike Bayer2014-07-101-3/+10
|
* imports gone badMike Bayer2014-07-101-2/+2
|
* - The :meth:`.TypeEngine.with_variant` method will now accept aMike Bayer2014-07-101-0/+7
| | | | | | type class as an argument which is internally converted to an instance, using the same convention long established by other constructs such as :class:`.Column`. fixes #3122
* - fully flake8 test/aaa_profilingMike Bayer2014-07-097-430/+581
|
* - support __only_on__ and __backend__ at the same timeMike Bayer2014-07-091-6/+1
|
* - Changed the default value of "raise_on_warnings" to False forMike Bayer2014-07-094-3/+9
| | | | | | | | MySQLconnector. This was set at True for some reason. The "buffered" flag unfortunately must stay at True as MySQLconnector does not allow a cursor to be closed unless all results are fully fetched. fixes #2515 - lots of MySQL tests seemed to not be hitting all backends, so we should be getting some mysqlconnector failures now
* -do an autoflake8 hereMike Bayer2014-07-081-141/+161
|
* - The "evaulator" for query.update()/delete() won't work with multi-tableMike Bayer2014-07-081-3/+16
| | | | | | | updates, and needs to be set to `synchronize_session=False` or `synchronize_session='fetch'`; this now raises an exception, with a message to change the synchronize setting. This will be only a warning in 0.9.7. fixes #3117
* Merge pull request #103 from tlocke/mastermike bayer2014-07-083-611/+757
|\ | | | | pg8000 passing test/sql
| * PEP8 tidy of subset of test/sql/*.pypr/103Tony Locke2014-07-074-602/+745
| |
| * pg8000 passing test/sqlTony Locke2014-07-064-13/+16
| |
* | - add postgresql_regconfig argument to PG dialect for match() operator,jonathan vanasco2014-07-081-0/+81
| | | | | | | | implements PG's to_tsquery('regconfig', 'arg') pattern. fixes #3078
* | Merge pull request #101 from ddimmich/mastermike bayer2014-07-071-2/+49
|\ \ | |/ |/| Postgres 9.4 Jsonb support
| * jsonb support for <@, ?| and ?& added.pr/101Damian Dimmich2014-07-011-0/+19
| | | | | | | | need to see if equality already works.
| * it's OK to pass a dict in - it does the right thing, no need to quote itDamian Dimmich2014-06-281-1/+1
| | | | | | | | in the tests.
| * minor cleanup of the jsonb - had extraneous operators that where copiedDamian Dimmich2014-06-281-1/+15
| | | | | | | | | | | | from hstore that don't apply. Add tests for ? and @> operators.
| * and tests for JSONB - as this is a superset of JSON i've subclassedDamian Dimmich2014-06-281-1/+15
| | | | | | | | the JSON tests as all of these should be applicable as well.
* | Merge pull request #100 from plaes/typosmike bayer2014-07-061-2/+2
|\ \ | | | | | | Typo fixes
| * | typo: s/thbe/thepr/100Priit Laes2014-06-281-1/+1
| | |
| * | typo: s/tranasction/transactionPriit Laes2014-06-281-2/+2
| | |
* | | Merged in therve/bug-3093/bug/3093 (pull request #24) Mike Bayer2014-07-061-2/+2
|\ \ \ | | | | | | | | Return the assigned value in MultableDict.setdefault
| * | | Return the assigned value in MultableDict.setdefaultThomas Herve2014-06-241-2/+2
| | |/ | |/|
* | | Merge pull request #99 from tlocke/mastermike bayer2014-07-061-234/+267
|\ \ \ | | | | | | | | pg8000 passing test/sql/test_types.py
| * | | PEP8 tidy of test/sql/test_types.pypr/99Tony Locke2014-06-231-221/+256
| | | |
| * | | pg8000 passing test/sql/test_types.pyTony Locke2014-06-231-13/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Opened up two tests that now pass with pg8000. Also, rewrote two tests to use actual tables rather than having a round trip in a single select statement. This is necessary for pg8000 because it sends strings to the server with type 'unknown' and lets the server work out the type.
* | | | - add test support for disconnect modificationMike Bayer2014-07-041-0/+25
| | | |
* | | | - rework the entire approach to #3076. As we need to catch all exceptionsMike Bayer2014-07-041-125/+267
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in all cases unconditionally, the number of use cases that go beyond what dbapi_error() is expecting has gone too far for an 0.9 release. Additionally, the number of things we'd like to track is really a lot more than the five arguments here, and ExecutionContext is really not suitable as totally public API for this. So restore dbapi_error to its old version, deprecate, and build out handle_error instead. This is a lot more extensible and doesn't get in the way of anything compatibility-wise.
* | | | - The mechanics of the :meth:`.ConnectionEvents.dbapi_error` handlerMike Bayer2014-07-031-0/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | have been enhanced such that the function handler is now capable of raising or returning a new exception object, which will replace the exception normally being thrown by SQLAlchemy. fixes #3076
* | | | - ensure ACID set up on this table for MySQLMike Bayer2014-07-011-2/+3
| | | |
* | | | - Fixed bug where items that were persisted, deleted, or had aMike Bayer2014-07-012-0/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | primary key change within a savepoint block would not participate in being restored to their former state (not in session, in session, previous PK) after the outer transaction were rolled back. fixes #3108
* | | | - repair the _enable_single_crit method, it was named the sameMike Bayer2014-06-301-0/+154
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | as the attribute and probably just replaced itself, so that is now _set_enable_single_crit - as a side effect of the main issue fixed here, correct the case in adjust_for_single_inheritance where the same mapper appears more than once in mapper_adapter_map; run through a set() for uniqueness. - Fixed bug in subquery eager loading in conjunction with :func:`.with_polymorphic`, the targeting of entities and columns in the subquery load has been made more accurate with respect to this type of entity and others. Fixes #3106
* | | - Fixed a bug within the custom operator plus :meth:`.TypeEngine.with_variant`Mike Bayer2014-06-271-1/+30
| | | | | | | | | | | | | | | | | | system, whereby using a :class:`.TypeDecorator` in conjunction with variant would fail with an MRO error when a comparison operator was used. fixes #3102
* | | - Fixed bug involving dynamic attributes, that was again a regressionMike Bayer2014-06-261-0/+17
| | | | | | | | | | | | | | | | | | of :ticket:`3060` from verision 0.9.5. A self-referential relationship with lazy='dynamic' would raise a TypeError within a flush operation. fixes #3099
* | | - Fixed bug when the declarative ``__abstract__`` flag was not beingMike Bayer2014-06-251-1/+24
| | | | | | | | | | | | | | | | | | | | | distinguished for when it was actually the value ``False``. The ``__abstract__`` flag needs to acutally evaluate to a True value at the level being tested. fixes #3097
* | | - add a test to confirm #3096, we definitely get a timedeltaMike Bayer2014-06-251-0/+10
| |/ |/|
* | - reverse course in #3061 so that we instead no longer set None in the attributeMike Bayer2014-06-234-38/+135
| | | | | | | | | | | | | | | | | | when we do a get; we return the None as always but we leave the dict blank and the loader callable still in place. The case for this implicit get on a pending object is not super common and there really should be no change in state at all when this operation proceeds. This change is more dramatic as it reverses a behavior SQLA has had since the first release. fixes #3061
* | - Reverted the change for :ticket:`3060` - this is a unit of workMike Bayer2014-06-231-0/+21
|/ | | | | | | fix that is updated more comprehensively in 1.0 via :ticket:`3061`. The fix in :ticket:`3060` unfortunately produces a new issue whereby an eager load of a many-to-one attribute can produce an event that is interpreted into an attribute change.
* - use new Or() directive to test for both SQL variants here, which can varyMike Bayer2014-06-211-7/+16
| | | | based on hash ordering of the ClassManager
* - fix test failuresMike Bayer2014-06-212-5/+5
|
* - Additional checks have been added for the case where an inheritingMike Bayer2014-06-209-69/+111
| | | | | | | | | | mapper is implicitly combining one of its column-based attributes with that of the parent, where those columns normally don't necessarily share the same value. This is an extension of an existing check that was added via :ticket:`1892`; however this new check emits only a warning, instead of an exception, to allow for applications that may be relying upon the existing behavior. fixes #3042
* - The :paramref:`.Column.nullable` flag is implicitly set to ``False``Mike Bayer2014-06-201-0/+18
| | | | | | | | | when that :class:`.Column` is referred to in an explicit :class:`.PrimaryKeyConstraint` for that table. This behavior now matches that of when the :class:`.Column` itself has the :paramref:`.Column.primary_key` flag set to ``True``, which is intended to be an exactly equivalent case. fixes #3023
* - Added a new type :class:`.postgresql.OID` to the Postgresql dialect.Mike Bayer2014-06-201-0/+13
| | | | | | | | While "oid" is generally a private type within PG that is not exposed in modern versions, there are some PG use cases such as large object support where these types might be exposed, as well as within some user-reported schema reflection use cases. fixes #3002
* - Fixed bug where column names added to ``mysql_length`` parameterMike Bayer2014-06-181-0/+33
| | | | | | | | on an index needed to have the same quoting for quoted names in order to be recognized. The fix makes the quotes optional but also provides the old behavior for backwards compatibility with those using the workaround. fixes #3085
* - Modified the behavior of :func:`.orm.load_only` such that primary keyMike Bayer2014-06-121-5/+36
| | | | | | | | | columns are always added to the list of columns to be "undeferred"; otherwise, the ORM can't load the row's identity. Apparently, one can defer the mapped primary keys and the ORM will fail, that hasn't been changed. But as load_only is essentially saying "defer all but X", it's more critical that PK cols not be part of this deferral. fixes #3080
* - fix this test for MySQL, needs InnoDBMike Bayer2014-05-301-3/+7
|
* - vastly improve the "safe close cursor" tests in test_reconnectMike Bayer2014-05-301-14/+57
| | | | | | | | | | | - Fixed bug which would occur if a DBAPI exception occurs when the engine first connects and does its initial checks, and the exception is not a disconnect exception, yet the cursor raises an error when we try to close it. In this case the real exception would be quashed as we tried to log the cursor close exception via the connection pool and failed, as we were trying to access the pool's logger in a way that is inappropriate in this very specific scenario. fixes #3063
* - The ``__mapper_args__`` dictionary is copied from a declarativeMike Bayer2014-05-301-0/+27
| | | | | | | | | mixin or abstract class when accessed, so that modifications made to this dictionary by declarative itself won't conflict with that of other mappings. The dictionary is modified regarding the ``version_id_col`` and ``polymorphic_on`` arguments, replacing the column within with the one that is officially mapped to the local class/table. fixes #3062
* Merge branch 'master' of https://github.com/tlocke/sqlalchemy into tlocke-masterMike Bayer2014-05-303-68/+58
|\
| * PEP 8 tidy of pg8000 dialect and postgresql/test_dialect.pypr/88Tony Locke2014-05-221-50/+40
| |
View Lorry Controller Status