summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* py2k: accept unicode literals on :func:`backref`, toopr/212Nils Philippsen2015-11-251-0/+23
| | | | | | | | Fixed bug where in Py2K a unicode literal would not be accepted as the string name of a class or other argument within declarative using :func:`.backref` on :func:`.relationship`. amends commit e6f67f48054d906856f879bc1803ea639aa4b670
* - Fixed joinedload bug which would occur when a. the query includesMike Bayer2015-11-211-1/+110
| | | | | | | | | | | | limit/offset criteria that forces a subquery b. the relationship uses "secondary" c. the primaryjoin of the relationship refers to a column that is either not part of the primary key, or is a PK col in a joined-inheritance subclass table that is under a different attribute name than the parent table's primary key column d. the query defers the columns that are present in the primaryjoin, typically via not being included in load_only(); the necessary column(s) would not be present in the subquery and produce invalid SQL. fixes #3592
* - don't create tables on compile-only testsMike Bayer2015-11-211-0/+2
|
* - try to get this to skip for oracleMike Bayer2015-11-201-1/+4
|
* - A rare case which occurs when a :meth:`.Session.rollback` fails in theMike Bayer2015-11-191-0/+25
| | | | | | | | | | | | scope of a :meth:`.Session.flush` operation that's raising an exception, as has been observed in some MySQL SAVEPOINT cases, prevents the original database exception from being observed when it was emitted during flush, but only on Py2K because Py2K does not support exception chaining; on Py3K the originating exception is chained. As a workaround, a warning is emitted in this specific case showing at least the string message of the original database error before we proceed to raise the rollback-originating exception. fixes #2696
* - Fixed the ``.python_type`` attribute of :class:`.postgresql.INTERVAL`Mike Bayer2015-11-191-0/+18
| | | | | | | | | to return ``datetime.timedelta`` in the same way as that of :obj:`.types.Interval.python_type`, rather than raising ``NotImplementedError``. fixes #3571 (cherry picked from commit 29d6f6e19b014bb5ce79032bd8803e32b4da0e5e)
* - rewrite the docs and add a test for the bake_queries=TrueMike Bayer2015-11-191-2/+46
| | | | | | | relationship flag; this flag *does* have an effect when the baked lazy loader plugin has been invoked. clarify the intent of this flag as an "opt out" but only has an effect when the baked system is loaded anyway. fixes #3572
* - Added support for reflecting the source of materialized viewsMike Bayer2015-11-181-0/+10
| | | | | | to the Postgresql version of the :meth:`.Inspector.get_view_definition` method. fixes #3587
* - extend pullreq github:213 to also include DATETIMEOFFSET and TIME,Mike Bayer2015-11-141-1/+87
| | | | | | which also accept zero precision - extend test case here to include a backend-agnostic suite - changelog for MSSQL date fix
* Merge remote-tracking branch 'origin/pr/213' into pr213Mike Bayer2015-11-141-0/+2
|\
| * Pass precision value to mssql.DATETIME2 when it is 0pr/213Jacobo de Vera2015-11-131-0/+2
| | | | | | | | | | The simple check on the precision results in DATETIME2(0) generating a DATETIME2 column, with default precision, which is 7.
* | - fix missing argument in TypeDecorator.copy(), fixes #3584, references #2919Mike Bayer2015-11-131-1/+15
|/
* - Fixed bug where the "single table inheritance" criteria would beMike Bayer2015-11-111-0/+15
| | | | | | | added onto the end of a query in some inappropriate situations, such as when querying from an exists() of a single-inheritance subclass. fixes #3582
* Merge branch 'pr204'Mike Bayer2015-10-292-0/+70
|\
| * - convert wrap_callable() to a general purpose update_wrapper-likeMike Bayer2015-10-292-60/+69
| | | | | | | | | | | | function; the caller still passes in the "wrapper" - move tests for wrap_callable() to be generic util tests - changelog for pullreq github:204
| * - wrap ColumnDefault empty arg callables like functools.wraps, setting ↵pr/204Martin J. Hsu2015-10-151-0/+61
| | | | | | | | __name__, __doc__, and __module__
* | - use is_() here to more clearly show what's going wrongMike Bayer2015-10-191-13/+25
| | | | | | | | on occasional pypy test runs
* | - Fixed regression in 1.0 where new feature of using "executemany"Mike Bayer2015-10-191-0/+88
| | | | | | | | | | | | | | | | | | for UPDATE statements in the ORM (e.g. :ref:`feature_updatemany`) would break on Postgresql and other RETURNING backends when using server-side version generation schemes, as the server side value is retrieved via RETURNING which is not supported with executemany. fixes #3556
* | - exclude this from unpredictable gcMike Bayer2015-10-111-1/+1
| |
* | - modernize some very old global-engine tests w/ bad teardownsMike Bayer2015-10-111-238/+260
| |
* | - repair flake8 issuesMike Bayer2015-10-111-44/+49
| |
* | - repair laziness about setting time zone here, which is leakingMike Bayer2015-10-111-9/+17
| | | | | | | | out depending on connection pool state
* | - Added the :paramref:`.AssociationProxy.info` parameter to theMike Bayer2015-10-091-0/+20
| | | | | | | | | | | | | | | | | | :class:`.AssociationProxy` constructor, to suit the :attr:`.AssociationProxy.info` accessor that was added in :ticket:`2971`. This is possible because :class:`.AssociationProxy` is constructed explicitly, unlike a hybrid which is constructed implicitly via the decorator syntax. fixes #3551
* | Merge remote-tracking branch 'origin/pr/203'Mike Bayer2015-10-092-3/+8
|\ \
| * | Remplement Query.one() in terms of .one_or_none()pr/203Eric Siegerman2015-09-282-3/+8
| |/ | | | | Thanks to Mike Bayer for suggesting a simpler refactoring.
* | - this was supposed to be client-side SQL default not server sideMike Bayer2015-10-091-1/+1
| |
* | - open up autoincrement for columns that have a default; autoinc is usuallyMike Bayer2015-10-082-12/+24
| | | | | | | | "auto" now so True can indicate the dialect would support this
* | - The system by which a :class:`.Column` considers itself to be anMike Bayer2015-10-0714-78/+353
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "auto increment" column has been changed, such that autoincrement is no longer implicitly enabled for a :class:`.Table` that has a composite primary key. In order to accommodate being able to enable autoincrement for a composite PK member column while at the same time maintaining SQLAlchemy's long standing behavior of enabling implicit autoincrement for a single integer primary key, a third state has been added to the :paramref:`.Column.autoincrement` parameter ``"auto"``, which is now the default. fixes #3216 - The MySQL dialect no longer generates an extra "KEY" directive when generating CREATE TABLE DDL for a table using InnoDB with a composite primary key with AUTO_INCREMENT on a column that isn't the first column; to overcome InnoDB's limitation here, the PRIMARY KEY constraint is now generated with the AUTO_INCREMENT column placed first in the list of columns.
* | - Fixed bug in Oracle dialect where reflection of tables and otherMike Bayer2015-10-051-0/+26
| | | | | | | | | | | | | | | | symbols with names quoted to force all-lower-case would not be identified properly in reflection queries. The :class:`.quoted_name` construct is now applied to incoming symbol names that detect as forced into all-lower-case within the "name normalize" process. fixes #3548
* | - limit the search for schemas to not include "temp", which is sort of an ↵Mike Bayer2015-09-282-24/+17
| | | | | | | | | | | | | | | | | | | | implicit schema - repair the CREATE INDEX ddl for schemas - update provisioning to include support for setting up ATTACH DATABASE up front for the test_schema; enable "schemas" testing for SQLite - changelog / migration notes for new SQLite schema support - include the "schema" as the "remote_schema" when we reflect SQLite FKs
* | Merge remote-tracking branch 'origin/pr/198' into pr198Mike Bayer2015-09-281-0/+5
|\ \
| * | Support get_schema_names for SQLitepr/198Brian Van Klaveren2015-09-091-0/+5
| | | | | | | | | Should return "main" and the names of attached databases.
* | | - fix bool testMike Bayer2015-09-271-1/+1
| | |
* | | - break out critical aspects of test_query into their own testsMike Bayer2015-09-273-1416/+1585
| |/ |/| | | | | | | finally, test_resultset and test_insert_exec. Update all idioms within these.
* | Fix sqlalchemy.ext.baked.Result.one_or_none() exception messagepr/202Eric Siegerman2015-09-241-3/+26
| | | | | | Also add a couple of missing tests.
* | - replicate Query.one_or_none to BakedQueryMike Bayer2015-09-241-0/+20
| | | | | | | | - changelog / version note finishing
* | Add Query.one_or_none()pr/201Eric Siegerman2015-09-241-0/+54
| |
* | - Fixed rare TypeError which could occur when stringifying certainMike Bayer2015-09-231-1/+11
| | | | | | | | | | kinds of internal column loader options within internal logging. fixes #3539
* | - The ``legacy_schema_aliasing`` flag, introduced in version 1.0.5Mike Bayer2015-09-193-12/+10
| | | | | | | | | | | | | | as part of :ticket:`3424` to allow disabling of the MSSQL dialect's attempts to create aliases for schema-qualified tables, now defaults to False; the old behavior is now disabled unless explicitly turned on. fixes #3434
* | - Added a new type-level modifier :meth:`.TypeEngine.evaluates_none`Mike Bayer2015-09-191-1/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | which indicates to the ORM that a positive set of None should be persisted as the value NULL, instead of omitting the column from the INSERT statement. This feature is used both as part of the implementation for :ticket:`3514` as well as a standalone feature available on any type. fixes #3250 - add new documentation section illustrating the "how to force null" use case of #3250 - alter our change from #3514 so that the class-level flag is now called "should_evaluate_none"; so that "evaluates_none" is now a generative method.
* | - The use of a :class:`.postgresql.ARRAY` object that refersMike Bayer2015-09-191-0/+26
| | | | | | | | | | | | | | to a :class:`.types.Enum` or :class:`.postgresql.ENUM` subtype will now emit the expected "CREATE TYPE" and "DROP TYPE" DDL when the type is used within a "CREATE TABLE" or "DROP TABLE". fixes #2729
* | - fixes for the ORM side test for #3531.Mike Bayer2015-09-171-3/+6
| |
* | - The :func:`.type_coerce` construct is now a fully fledged CoreMike Bayer2015-09-163-2/+140
| | | | | | | | | | | | | | | | | | | | | | expression element which is late-evaluated at compile time. Previously, the function was only a conversion function which would handle different expression inputs by returning either a :class:`.Label` of a column-oriented expression or a copy of a given :class:`.BindParameter` object, which in particular prevented the operation from being logically maintained when an ORM-level expression transformation would convert a column to a bound parameter (e.g. for lazy loading). fixes #3531
* | - profile updateMike Bayer2015-09-081-1/+1
| |
* | - Internal calls to "bookkeeping" functions withinMike Bayer2015-09-081-2/+3
| | | | | | | | | | | | | | | | :meth:`.Session.bulk_save_objects` and related bulk methods have been scaled back to the extent that this functionality is not currently used, e.g. checks for column default values to be fetched after an INSERT or UPDATE statement. fixes #3526
* | - Fixed bug in :meth:`.Session.bulk_save_objects` where a mappedMike Bayer2015-09-081-1/+53
| | | | | | | | | | | | | | column that had some kind of "fetch on update" value and was not locally present in the given object would cause an AttributeError within the operation. fixes #3525
* | - rewrite some profiles that went *down*! woopMike Bayer2015-09-031-5/+5
| |
* | Merge branch 'ticket_2677'Mike Bayer2015-09-026-52/+626
|\ \
| * | - The :class:`.SessionEvents` suite now includes events to allowticket_2677Mike Bayer2015-09-026-52/+626
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | unambiguous tracking of all object lifecycle state transitions in terms of the :class:`.Session` itself, e.g. pending, transient, persistent, detached. The state of the object within each event is also defined. fixes #2677 - Added a new session lifecycle state :term:`deleted`. This new state represents an object that has been deleted from the :term:`persistent` state and will move to the :term:`detached` state once the transaction is committed. This resolves the long-standing issue that objects which were deleted existed in a gray area between persistent and detached. The :attr:`.InstanceState.persistent` accessor will **no longer** report on a deleted object as persistent; the :attr:`.InstanceState.deleted` accessor will instead be True for these objects, until they become detached. - The :paramref:`.Session.weak_identity_map` parameter is deprecated. See the new recipe at :ref:`session_referencing_behavior` for an event-based approach to maintaining strong identity map behavior. references #3517
* | | - Fixed regression in 1.0-released default-processor for multi-VALUESMike Bayer2015-08-312-16/+52
|/ / | | | | | | | | | | | | | | insert statement, :ticket:`3288`, where the column type for the default-holding column would not be propagated to the compiled statement in the case where the default was being used, leading to bind-level type handlers not being invoked. fixes #3520
View Lorry Controller Status