summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Accept unicode in CascadeOptionspr/160Julien Castets2015-03-161-1/+9
|
* - Added a new extension suite :mod:`sqlalchemy.ext.baked`. ThisMike Bayer2015-03-113-2/+785
| | | | | | | | simple but unusual system allows for a dramatic savings in Python overhead for the construction and processing of orm :class:`.Query` objects, from query construction up through rendering of a string SQL statement. fixes #3054
* - Added a new entry ``"entity"`` to the dictionaries returned byMike Bayer2015-03-111-12/+21
| | | | | | | | | :attr:`.Query.column_descriptions`. This refers to the primary ORM mapped class or aliased class that is referred to by the expression. Compared to the existing entry for ``"type"``, it will always be a mapped entity, even if extracted from a column expression, or None if the given expression is a pure core expression. references #3320
* - The Postgresql :class:`.postgresql.ENUM` type will emit aMike Bayer2015-03-112-1/+100
| | | | | | | | | | | | DROP TYPE instruction when a plain ``table.drop()`` is called, assuming the object is not associated directly with a :class:`.MetaData` object. In order to accomodate the use case of an enumerated type shared between multiple tables, the type should be associated directly with the :class:`.MetaData` object; in this case the type will only be created at the metadata level, or if created directly. The rules for create/drop of Postgresql enumerated types have been highly reworked in general. fixes #3319
* - Added a new event suite :class:`.QueryEvents`. TheMike Bayer2015-03-101-1/+37
| | | | | | | | | | | :meth:`.QueryEvents.before_compile` event allows the creation of functions which may place additional modifications to :class:`.Query` objects before the construction of the SELECT statement. It is hoped that this event be made much more useful via the advent of a new inspection system that will allow for detailed modifications to be made against :class:`.Query` objects in an automated fashion. fixes #3317
* - The subquery wrapping which occurs when joined eager loadingMike Bayer2015-03-102-12/+38
| | | | | | | | | is used with a one-to-many query that also features LIMIT, OFFSET, or DISTINCT has been disabled in the case of a one-to-one relationship, that is a one-to-many with :paramref:`.relationship.uselist` set to False. This will produce more efficient queries in these cases. fixes #3249
* - Fixed bug where the session attachment error "object is alreadyMike Bayer2015-03-101-1/+20
| | | | | | | attached to session X" would fail to prevent the object from also being attached to the new session, in the case that execution continued after the error raise occurred. fixes #3301
* - Fixed bug where using an ``__abstract__`` mixin in the middleMike Bayer2015-03-101-0/+41
| | | | | | | of a declarative inheritance hierarchy would prevent attributes and configuration being correctly propagated from the base class to the inheriting class. fixes #3219 fixes #3240
* Merge branch 'postgres-concurrently' of ↵Mike Bayer2015-03-101-0/+10
|\ | | | | | | https://bitbucket.org/iurisilvio/sqlalchemy into pr45
| * Dialect option `postgresql_concurrently` to `Index` construct.Iuri de Silvio2015-02-251-0/+10
| |
* | Fix slice addressing of _AssociationList with python3Gilles Dartiguelongue2015-03-101-0/+16
| |
* | Merge branch 'sqlite-partial-indexes' of ↵Mike Bayer2015-03-101-1/+22
|\ \ | | | | | | | | | https://bitbucket.org/groner/sqlalchemy into pr42
| * | Test for partial index support in sqlite dialects.Kai Groner2015-01-261-1/+22
| | |
* | | - updated countsMike Bayer2015-03-091-137/+137
| | |
* | | - pick around gaining modest dings in callcounts here and thereMike Bayer2015-03-092-102/+99
| | |
* | | - start locking down querying for cols after observing yesterdaysMike Bayer2015-03-092-196/+361
| | | | | | | | | | | | | | | callcount bump due to the slots thing - rewrite profiles using new technique
* | | - we really don't want to force lib here, but we do needMike Bayer2015-03-091-2/+1
| | | | | | | | | | | | | | | it for the plain "pytest" case, so do an append instead of an insert - add a new tox file to do a full regen of callcounts
* | | - fix some more result_map callsMike Bayer2015-03-083-14/+14
| | |
* | | - rename _select_wrapsMike Bayer2015-03-081-0/+61
| | | | | | | | | | | | | | | - replace force_result_map with a mini-API for nested result sets, add coverage
* | | fooMike Bayer2015-03-086-33/+33
| | |
* | | - the change for #918 was of course not nearly that simple.Mike Bayer2015-03-072-4/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "wrapping" employed by the mssql and oracle dialects using the "iswrapper" argument was not being used intelligently by the compiler, and the result map was being written incorrectly, using *more* columns in the result map than were actually returned by the statement, due to "row number" columns that are inside the subquery. The compiler now writes out result map on the "top level" select in all cases fully, and for the mssql/oracle wrapping case extracts out the "proxied" columns in a second step, which only includes those columns that are proxied outwards to the top level. This change might have implications for 3rd party dialects that might be imitating oracle's approach. They can safely continue to use the "iswrapper" kw which is now ignored, but they may need to also add the _select_wraps argument as well.
* | | - do a full rewrite of callcountsMike Bayer2015-03-071-94/+93
| | |
* | | - The SQL compiler now generates the mapping of expected columnspositional_targetingMike Bayer2015-03-072-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | such that they are matched to the received result set positionally, rather than by name. Originally, this was seen as a way to handle cases where we had columns returned with difficult-to-predict names, though in modern use that issue has been overcome by anonymous labeling. In this version, the approach basically reduces function call count per-result by a few dozen calls, or more for larger sets of result columns. The approach still degrades into a modern version of the old approach if textual elements modify the result map, or if any discrepancy in size exists between the compiled set of columns versus what was received, so there's no issue for partially or fully textual compilation scenarios where these lists might not line up. fixes #918 - callcounts still need to be adjusted down for this so zoomark tests won't pass at the moment
* | | - add a skip for JSONB on pg8000 if we are on 1.10.1 or earlierMike Bayer2015-03-022-0/+9
| | |
* | | Merge remote-tracking branch 'origin/pr/132' into pr132Mike Bayer2015-03-021-3/+6
|\ \ \
| * | | pg8000 client_encoding in create_engine()Tony Locke2014-12-161-3/+6
| | | | | | | | | | | | | | | | | | | | The pg8000 dialect now supports the setting of the PostgreSQL parameter client_encoding from create_engine().
* | | | - squash-merge the final row_proc integration branch. this isMike Bayer2015-03-012-11/+35
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a much more modest outcome than what we started with. The work of create_row_processor() for ColumnProperty objects is essentially done at query setup time combined with some lookups in _instance_processor(). - to allow this change for deferred columns, deferred columns no longer search for themselves in the result. If they've been set up as deferred without any explicit directive to undefer them, then this is what was asked for. if we don't do this, then we're stuck with this performance penalty for all deferred columns which in the vast majority of typical use cases (e.g. loading large, legacy tables or tables with many/large very seldom used values) won't be present in the result and won't be accessed at all.
* | | - repair issue in declared_attr.cascading such that within aMike Bayer2015-02-241-0/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | subclass, the value returned by the descriptor is not available because the superclass is already mapped with the InstrumentedAttribute, until the subclass is mapped. We add a setattr() to set up that attribute so that the __mapper_args__ hook and possibly others have access to the "cascaded" version of the attribute within the call.
* | | - Fixed bugs in ORM object comparisons where comparison ofMike Bayer2015-02-202-10/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | many-to-one ``!= None`` would fail if the source were an aliased class, or if the query needed to apply special aliasing to the expression due to aliased joins or polymorphic querying; also fixed bug in the case where comparing a many-to-one to an object state would fail if the query needed to apply special aliasing due to aliased joins or polymorphic querying. fixes #3310
* | | - Fixed bug where internal assertion would fail in the case whereMike Bayer2015-02-201-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | an ``after_rollback()`` handler for a :class:`.Session` incorrectly adds state to that :class:`.Session` within the handler, and the task to warn and remove this state (established by :ticket:`2389`) attempts to proceed. fixes #3309
* | | - expect_warnings was not expecting and neither was assert_warningsMike Bayer2015-02-191-4/+4
| | | | | | | | | | | | asserting.
* | | - repair merge failureMike Bayer2015-02-191-22/+6
| | |
* | | - autopep8Mike Bayer2015-02-191-39/+43
| | |
* | | - Mapped state internals have been reworked to allow for a 50% reductionMike Bayer2015-02-184-67/+141
| | | | | | | | | | | | | | | | | | | | | | | | in callcounts specific to the "expiration" of objects, as in the "auto expire" feature of :meth:`.Session.commit` and for :meth:`.Session.expire_all`, as well as in the "cleanup" step which occurs when object states are garbage collected. fixes #3307
* | | - add the test_expire_lots test for comparisonMike Bayer2015-02-182-0/+71
| | |
* | | - additional mysql cast-related test fixesMike Bayer2015-02-092-0/+9
| | |
* | | - The MySQL dialect now supports CAST on types that are constructedMike Bayer2015-02-091-1/+11
| | | | | | | | | | | | as :class:`.TypeDecorator` objects.
* | | - test skips for MySQL w new cast warningMike Bayer2015-02-091-0/+16
| | |
* | | - A warning is emitted when :func:`.cast` is used with the MySQLMike Bayer2015-02-091-29/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | dialect on a type where MySQL does not support CAST; MySQL only supports CAST on a subset of datatypes. SQLAlchemy has for a long time just omitted the CAST for unsupported types in the case of MySQL. While we don't want to change this now, we emit a warning to show that it's taken place. A warning is also emitted when a CAST is used with an older MySQL version (< 4) that doesn't support CAST at all, it's skipped in this case as well. fixes #3237
* | | - flake8Mike Bayer2015-02-091-74/+99
| | |
* | | - Literal values within a :class:`.DefaultClause`, which is invokedMike Bayer2015-02-091-3/+70
| | | | | | | | | | | | | | | | | | | | | when using the :paramref:`.Column.server_default` parameter, will now be rendered using the "inline" compiler, so that they are rendered as-is, rather than as bound parameters. fixes #3087
* | | - test + changelogMike Bayer2015-02-081-0/+14
| | |
* | | - cx_Oracle.makedsn can now be passed service_name; squashSławek Ehlert2014-04-021-0/+20
| | | | | | | | | | | | commit of pr152
* | | - make even more tablesMike Bayer2015-02-071-27/+30
| | |
* | | - break up the tables here to avoid the error we're gettingMike Bayer2015-02-061-15/+24
| | | | | | | | | | | | on jenkins
* | | - The MySQL dialect now renders TIMESTAMP with NULL / NOT NULL inMike Bayer2015-02-052-29/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | all cases, so that MySQL 5.6.6 with the ``explicit_defaults_for_timestamp`` flag enabled will will allow TIMESTAMP to continue to work as expected when ``nullable=False``. Existing applications are unaffected as SQLAlchemy has always emitted NULL for a TIMESTAMP column that is ``nullable=True``. fixes #3155
* | | - Fixed bug in :class:`.Connection` and pool where theMike Bayer2015-02-042-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | :meth:`.Connection.invalidate` method, or an invalidation due to a database disconnect, would fail if the ``isolation_level`` parameter had been used with :meth:`.Connection.execution_options`; the "finalizer" that resets the isolation level would be called on the no longer opened connection. fixes #3302
* | | - A warning is emitted if the ``isolation_level`` parameter is usedMike Bayer2015-02-043-7/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | with :meth:`.Connection.execution_options` when a :class:`.Transaction` is in play; DBAPIs and/or SQLAlchemy dialects such as psycopg2, MySQLdb may implicitly rollback or commit the transaction, or not change the setting til next transaction, so this is never safe. - Added new parameter :paramref:`.Session.connection.execution_options` which may be used to set up execution options on a :class:`.Connection` when it is first checked out, before the transaction has begun. This is used to set up options such as isolation level on the connection before the transaction starts. - added new documentation section detailing best practices for setting transaction isolation with sessions. fixes #3296
* | | - Fixed bug in lazy loading SQL construction whereby a complexMike Bayer2015-02-022-3/+73
| | | | | | | | | | | | | | | | | | | | | | | | primaryjoin that referred to the same "local" column multiple times in the "column that points to itself" style of self-referential join would not be substituted in all cases. The logic to determine substitutions here has been reworked to be more open-ended. fixes #3300
* | | - Repaired support for Postgresql UUID types in conjunction withMike Bayer2015-02-011-6/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the ARRAY type when using psycopg2. The psycopg2 dialect now employs use of the psycopg2.extras.register_uuid() hook so that UUID values are always passed to/from the DBAPI as UUID() objects. The :paramref:`.UUID.as_uuid` flag is still honored, except with psycopg2 we need to convert returned UUID objects back into strings when this is disabled. fixes #2940
View Lorry Controller Status