summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed bug which would cause an eagerly loaded many-to-one attributeMike Bayer2016-02-171-2/+147
| | | | | | | | to not be loaded, if the joined eager load were from a row where the same entity were present multiple times, some calling for the attribute to be eagerly loaded and others not. The logic here is revised to take in the attribute even though a different loader path has handled the parent entity already. fixes #3431
* - handle parameter sets that aren't correctly formed, so thatMike Bayer2016-02-171-1/+27
| | | | | for example an exception object made within a test suite can still repr (error seen in Keystone)
* - do the trailing comma logic of tuple repr() exactlyMike Bayer2016-02-171-0/+18
|
* - All string formatting of bound parameter sets and result rows forMike Bayer2016-02-171-1/+85
| | | | | | | | | logging, exception, and ``repr()`` purposes now truncate very large scalar values within each collection, including an "N characters truncated" notation, similar to how the display for large multiple-parameter sets are themselves truncated. fixes #2837
* Add `sqlalchemy.ext.mutable.MutableSet`pr/236Jeong YunWon2016-02-131-1/+195
| | | | from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297
* Add `sqlalchemy.ext.mutable.MutableList`Jeong YunWon2016-02-131-1/+218
|
* - Fixed bug in :meth:`.Session.merge` where an object with a compositeMike Bayer2016-02-111-1/+50
| | | | | | | | primary key that has values for some but not all of the PK fields would emit a SELECT statement leaking the internal NEVER_SET symbol into the query, rather than detecting that this object does not have a searchable primary key and no SELECT should be emitted. fixes #3647
* - CTE functionality has been expanded to support all DML, allowingMike Bayer2016-02-112-4/+153
| | | | | | | INSERT, UPDATE, and DELETE statements to both specify their own WITH clause, as well as for these statements themselves to be CTE expressions when they include a RETURNING clause. fixes #2551
* - Fixed bug in :func:`.expression.text` construct where a double-colonMike Bayer2016-02-091-0/+11
| | | | | | expression would not escape properly, e.g. ``some\:\:expr``, as is most commonly required when rendering Postgresql-style CAST expressions. fixes #3644
* - A refinement to the logic which adds columns to the resulting SQL whenMike Bayer2016-02-091-7/+137
| | | | | | | | | | | | | :meth:`.Query.distinct` is combined with :meth:`.Query.order_by` such that columns which are already present will not be added a second time, even if they are labeled with a different name. Regardless of this change, the extra columns added to the SQL have never been returned in the final result, so this change only impacts the string form of the statement as well as its behavior when used in a Core execution context. Additionally, columns are no longer added when the DISTINCT ON format is used, provided the query is not wrapped inside a subquery due to joined eager loading. fixes #3641
* - add missing __backend__ directives for SQL serverMike Bayer2016-02-082-0/+6
|
* - add missing __backend__ directives so that oracle tests actually run with ↵Mike Bayer2016-02-081-0/+17
| | | | --backend-only
* - detect "Enterprise" and assume compression stuff isn't availableMike Bayer2016-02-081-0/+6
| | | | if not
* - adjust the MultiSchemaTest to handle multiple test_schemas / processes at theMike Bayer2016-02-081-5/+6
| | | | same time
* - adjust to allow dblink tests to work with multiprocess users.Mike Bayer2016-02-081-9/+3
| | | | | | unfortunately the synonym doesn't work for SQL statements here when the dblink is on a different user, testing this is not really critical so just removed it.
* - add literal_binds for delete() statements in addition to insert()/update()Mike Bayer2016-02-031-16/+25
| | | | | - move tests to CRUDTest - changelog, fixes #3643
* fix passing literal_binds flag through for update and insertpr/232Tim Tate2016-02-021-0/+16
|
* - test fixes for metadata.enums value now being a listMike Bayer2016-02-022-24/+20
| | | | - modernize those tests as well
* - add changelog and migration notes for new Enum features,Mike Bayer2016-02-022-36/+158
| | | | | | | | | | | | fixes #3095, #3292 - reorganize enum constructor to again work with the MySQL ENUM type - add a new create_constraint flag to Enum to complement that of Boolean - reinstate the CHECK constraint tests for enum, these already fail /skip against the MySQL backend - simplify lookup rules in Enum, have them apply to all varieties of Enum equally
* - Initial implementation of support for PEP-435 enumerated typesAlex Grönholm2016-02-021-29/+56
| | | | within the Enum type.
* - Fixed issue where inadvertent use of the Python ``__contains__``Mike Bayer2016-02-022-1/+32
| | | | | | | | | override with a column expression (e.g. by using ``'x' in col``) would cause an endless loop in the case of an ARRAY type, as Python defers this to ``__getitem__`` access which never raises for this type. Overall, all use of ``__contains__`` now raises NotImplementedError. fixes #3642
* - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-291-0/+10
| | | | | | | removed; this has emitted a warning for many years and projects should be calling upon ``sqlalchemy.dialects.postgresql``. Engine URLs of the form ``postgres://`` will still continue to function, however.
* - revert the change first made in a6fe4dc, as we are now generalizingMike Bayer2016-01-284-4/+61
| | | | | | | | | | | | | | | | | | | | | | | the warning here to all safe_reraise() cases in Python 2. - Revisiting :ticket:`2696`, first released in 1.0.10, which attempts to work around Python 2's lack of exception context reporting by emitting a warning for an exception that was interrupted by a second exception when attempting to roll back the already-failed transaction; this issue continues to occur for MySQL backends in conjunction with a savepoint that gets unexpectedly lost, which then causes a "no such savepoint" error when the rollback is attempted, obscuring what the original condition was. The approach has been generalized to the Core "safe reraise" function which takes place across the ORM and Core in any place that a transaction is being rolled back in response to an error which occurred trying to commit, including the context managers provided by :class:`.Session` and :class:`.Connection`, and taking place for operations such as a failure on "RELEASE SAVEPOINT". Previously, the fix was only in place for a specific path within the ORM flush/commit process; it now takes place for all transational context managers as well. fixes #2696
* - restore the use of PYTHONNOUSERSITE that was removedMike Bayer2016-01-271-0/+6
| | | | | | | | | | in df3f125bd84fc7ec5d45592c5774daf3a39d9bc9, this flag is explicitly checked within conftest.py and we need to continue to use it, otherwise a tox build inside of .tox that isn't usedevelop is ignored, including C extensions - rework the whole system of running with coverage, so that with coverage, we *are* using usedevelop, but also make sure we rm the .so files for nocext, make sure we --cov-append, etc.
* - rework ColumnCollection to no longer persist "all_col_set"; we don'tMike Bayer2016-01-261-0/+19
| | | | | | | | | | | | | need this collection except in the extend/update uses where we create it ad-hoc. simplifies pickling. Compatibility with 1.0 should be OK as ColumnColleciton uses __getstate__ in any case and the __setstate__ contract hasn't changed. - Fixed bug in :class:`.Table` metadata construct which appeared around the 0.9 series where adding columns to a :class:`.Table` that was unpickled would fail to correctly establish the :class:`.Column` within the 'c' collection, leading to issues in areas such as ORM configuration. This could impact use cases such as ``extend_existing`` and others. fixes #3632
* - The workaround for right-nested joins on SQLite, where they are rewrittenMike Bayer2016-01-262-93/+146
| | | | | | | | | | as subqueries in order to work around SQLite's lack of support for this syntax, is lifted when SQLite version 3.7.16 or greater is detected. fixes #3634 - The workaround for SQLite's unexpected delivery of column names as ``tablename.columnname`` for some kinds of queries is now disabled when SQLite version 3.10.0 or greater is detected. fixes #3633
* - add a new qualifier "native" vs. "dbapi" unicode to avoidMike Bayer2016-01-241-468/+404
| | | | | | profiling problems here - add extras_require to setup.py for the most common DBAPIs - rework tox.ini to use extras, specify a test matrix built in
* - fix array test that was essentially taking a weird guessMike Bayer2016-01-231-2/+2
| | | | | | at the primary key of a row based on other tests invoking around it (cherry picked from commit 7d70dfd412c05fd8349339da01b472bd3df02082)
* - fix stray connectionMike Bayer2016-01-231-1/+4
|
* - use regex here, columns dont matter, keep coming up with different orderingsMike Bayer2016-01-231-3/+3
|
* - native unicode expectations are too difficult to maintainMike Bayer2016-01-231-60/+0
| | | | w/ the number of drivers /DBURIs / python versions
* - move out match compiler test to test_compilerMike Bayer2016-01-232-23/+11
| | | | - test_query isn't assertscompiledsql
* - make this test deterministicMike Bayer2016-01-211-3/+3
|
* - add a forwards-test here as wellMike Bayer2016-01-211-0/+4
|
* - documenation updates to clarify specific SQLite versionsMike Bayer2016-01-211-10/+20
| | | | | | | | | that have problems with right-nested joins and UNION column keys; references #3633 references #3634. backport from 1.1 to 0.9 announcing 1.1 as where these behaviors will be retired based on version-specific checks - fix test_resultset so that it passes when SQLite 3.10.0 is present, references #3633
* - Added new parameter :paramref:`.orm.mapper.passive_deletes` toMike Bayer2016-01-201-0/+236
| | | | | | | | available mapper options. This allows a DELETE to proceed for a joined-table inheritance mapping against the base table only, while allowing for ON DELETE CASCADE to handle deleting the row from the subclass tables. fixes #2349
* - The unsupported Sybase dialect now raises ``NotImplementedError``Mike Bayer2016-01-201-3/+11
| | | | | when attempting to compile a query that includes "offset"; Sybase has no straightforward "offset" feature. fixes #2278
* - calling str() on a core sql construct has been made more "friendly",Mike Bayer2016-01-193-9/+79
| | | | | | | | | | when the construct contains non-standard sql elements such as returning, array index operations, or dialect-specific or custom datatypes. a string is now returned in these cases rendering an approximation of the construct (typically the postgresql-style version of it) rather than raising an error. fixes #3631 - add within_group to top-level imports - add eq_ignore_whitespace to sqlalchemy.testing imports
* - Fixed issue where two same-named relationships that refer toMike Bayer2016-01-191-0/+39
| | | | | | | | a base class and a concrete-inherited subclass would raise an error if those relationships were set up using "backref", while setting up the identical configuration using relationship() instead with the conflicting names would succeed, as is allowed in the case of a concrete mapping. fixes #3630
* - The ``str()`` call for :class:`.Query` will now take into accountMike Bayer2016-01-191-2/+66
| | | | | | | | | | | | the :class:`.Engine` to which the :class:`.Session` is bound, when generating the string form of the SQL, so that the actual SQL that would be emitted to the database is shown, if possible. Previously, only the engine associated with the :class:`.MetaData` to which the mappings are associated would be used, if present. If no bind can be located either on the :class:`.Session` or on the :class:`.MetaData` to which the mappings are associated, then the "default" dialect is used to render the SQL, as was the case previously. fixes #3081
* - Fixed bug where some exception re-raise scenarios would attachMike Bayer2016-01-181-0/+59
| | | | | | | | the exception to itself as the "cause"; while the Python 3 interpreter is OK with this, it could cause endless loops in iPython. fixes #3625 - add tests for reraise, raise_from_cause - raise_from_cause is the same on py2k/3k, use just one function
* - A deep improvement to the recently added :meth:`.TextClause.columns`Mike Bayer2016-01-144-387/+549
| | | | | | | | | | | | | | | | | | | method, and its interaction with result-row processing, now allows the columns passed to the method to be positionally matched with the result columns in the statement, rather than matching on name alone. The advantage to this includes that when linking a textual SQL statement to an ORM or Core table model, no system of labeling or de-duping of common column names needs to occur, which also means there's no need to worry about how label names match to ORM columns and so-forth. In addition, the :class:`.ResultProxy` has been further enhanced to map column and string keys to a row with greater precision in some cases. fixes #3501 - reorganize the initialization of ResultMetaData for readability and complexity; use the name "cursor_description", define the task of "merging" cursor_description with compiled column information as its own function, and also define "name extraction" as a separate task. - fully change the name we use in the "ambiguous column" error to be the actual name that was ambiguous, modify the C ext also
* - there was a DATEPART test after all, fix formatMike Bayer2016-01-141-1/+1
|
* - changelog for pr bitbucket:70, fixes #3624Mike Bayer2016-01-121-0/+12
|
* - refactor a bit the loader options system to make it a bit moreMike Bayer2016-01-101-3/+125
| | | | | intelligible, given the fixes for ref #3623. unfortunately the system is still quite weird even though it was rewritten to be... less weird
* - Fixed regression since 0.9 where the 0.9 style loader optionsMike Bayer2016-01-091-0/+58
| | | | | | | system failed to accommodate for multiple :func:`.undefer_group` loader options in a single query. Multiple :func:`.undefer_group` options will now be taken into account even against the same entity. fixes #3623
* - Multi-tenancy schema translation for :class:`.Table` objects is added.Mike Bayer2016-01-084-5/+347
| | | | | | | | | This supports the use case of an application that uses the same set of :class:`.Table` objects in many schemas, such as schema-per-user. A new execution option :paramref:`.Connection.execution_options.schema_translate_map` is added. fixes #2685 - latest tox doesn't like the {posargs} in the profile rerunner
* - pg8000 fixes for jsonMike Bayer2016-01-071-0/+4
|
* - add a do-nothing for mock url _instantiate_pluginsMike Bayer2016-01-061-0/+1
|
* - Added a new entrypoint system to the engine to allow "plugins" toMike Bayer2016-01-061-8/+35
| | | | | | | | | | | be stated in the query string for a URL. Custom plugins can be written which will be given the chance up front to alter and/or consume the engine's URL and keyword arguments, and then at engine create time will be given the engine itself to allow additional modifications or event registration. Plugins are written as a subclass of :class:`.CreateEnginePlugin`; see that class for details. fixes #3536
View Lorry Controller Status