summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* changelog for thisMike Bayer2013-06-101-1/+36
|
* changelogMike Bayer2013-06-102-0/+16
|
* Fixed bug where sending a composite attribute into :meth:`.Query.order_by`Mike Bayer2013-06-102-0/+14
| | | | | would produce a parenthesized expression not accepted by some databases. [ticket:2754]
* Fixed the interaction between composite attributes andMike Bayer2013-06-102-0/+19
| | | | | | the :func:`.aliased` function. Previously, composite attributes wouldn't work correctly in comparison operations when aliasing was applied. Also in 0.8.2. [ticket:2755]
* - get_unique_constraints() pull requestMike Bayer2013-06-091-0/+7
| | | | | | - version (0.9 for now) - changelog - move the test into the test suite so that all dialects can take advantage of it
* Added pool logging for "rollback-on-return" and the less usedMike Bayer2013-06-091-0/+8
| | | | | | "commit-on-return". This is enabled with the rest of pool "debug" logging. [ticket:2752]
* ...and...its a behavioral improvementMike Bayer2013-06-081-92/+88
|
* fix this exampleMike Bayer2013-06-081-2/+2
|
* mention right joins, make it clear we're talking about left outer join as ↵Mike Bayer2013-06-081-5/+13
| | | | the bigger issue
* oracle 9 does support this, oracle 8 is a special case.Mike Bayer2013-06-081-5/+6
|
* - tests for the alias() APIMike Bayer2013-06-081-30/+189
| | | | - docs docs docs
* formattingMike Bayer2013-06-081-3/+3
|
* changelogMike Bayer2013-06-082-0/+17
|
* - changelog for [ticket:2704]Mike Bayer2013-06-082-0/+18
| | | | - use an isinstance() check, concerned a TypeError might be indiscriminate
* also clarified the changelog regarding Cls.scalar != 'value'Mike Bayer2013-06-081-1/+7
|
* Added additional criterion to the ==, != comparators, used withMike Bayer2013-06-081-0/+21
| | | | | | | | | | | | | | | | | | | scalar values, for comparisons to None to also take into account the association record itself being non-present, in addition to the existing test for the scalar endpoint on the association record being NULL. Previously, comparing ``Cls.scalar == None`` would return records for which ``Cls.associated`` were present and ``Cls.associated.scalar`` is None, but not rows for which ``Cls.associated`` is non-present. More significantly, the inverse operation ``Cls.scalar != None`` *would* return ``Cls`` rows for which ``Cls.associated`` was non-present. Additionally, added a special use case where you can call ``Cls.scalar.has()`` with no arguments, when ``Cls.scalar`` is a column-based value - this returns whether or not ``Cls.associated`` has any rows present, regardless of whether or not ``Cls.associated.scalar`` is NULL or not. [ticket:2751]
* - Fixed an obscure bug where the wrong results would beMike Bayer2013-06-071-0/+13
| | | | | | | | | | | fetched when joining/joinedloading across a many-to-many relationship to a single-table-inheriting subclass with a specific discriminator value, due to "secondary" rows that would come back. The "secondary" and right-side tables are now inner joined inside of parenthesis for all ORM joins on many-to-many relationships so that the left->right join can accurately filtered. [ticket:2369]
* When querying the information schema on SQL Server 2000, removedMike Bayer2013-06-062-0/+19
| | | | | | | a CAST call that was added in 0.8.1 to help with driver issues, which apparently is not compatible on 2000. The CAST remains in place for SQL Server 2005 and greater. [ticket:2747]
* The ``deferrable`` keyword argument on :class:`.ForeignKey` andMike Bayer2013-06-032-0/+22
| | | | | | | | :class:`.ForeignKeyConstraint` will not render the ``DEFERRABLE`` keyword on the MySQL dialect. For a long time we left this in place because a non-deferrable foreign key would act very differently than a deferrable one, but some environments just disable FKs on MySQL, so we'll be less opinionated here. [ticket:2721]
* Fixed bug where :class:`.MutableDict` didn't report a change eventMike Bayer2013-06-032-0/+14
| | | | | when ``clear()`` was called. [ticket:2730]
* Fixed bug whereby joining a select() of a table "A" with multipleMike Bayer2013-06-032-0/+20
| | | | | | | | foreign key paths to a table "B", to that table "B", would fail to produce the "ambiguous join condition" error that would be reported if you join table "A" directly to "B"; it would instead produce a join condition with multiple criteria. [ticket:2738]
* Fixed bug whereby using :meth:`.MetaData.reflect` across a remoteMike Bayer2013-06-032-0/+17
| | | | | | schema as well as a local schema could produce wrong results in the case where both schemas had a table of the same name. [ticket:2728]
* - remove the ``__iter__()`` with notimplemented since it interferesMike Bayer2013-06-032-0/+30
| | | | with legitimate iterable detection, [ticket:2726]
* - add changelog/migration noteMike Bayer2013-06-032-0/+53
| | | | - inline the label check
* - fdb is now official, [ticket:2504]Mike Bayer2013-06-033-5/+26
| | | | | - restore the rollback cleanup handler, pg8000 is mostly obsolete as a dialect and the firebird drivers need it
* 0.8 changelog in 0.9Mike Bayer2013-05-311-0/+11
|
* Fixed a regression caused by [ticket:2682] whereby theMike Bayer2013-05-311-0/+9
| | | | | | | evaluation invoked by :meth:`.Query.update` and :meth:`.Query.delete` would hit upon unsupported ``True`` and ``False`` symbols which now appear due to the usage of ``IS``. [ticket:2737]
* The "auto-aliasing" behavior of the :class:`.Query.select_from`Mike Bayer2013-05-302-3/+107
| | | | | | method has been turned off. The specific behavior is now availble via a new method :class:`.Query.select_entity_from`. [ticket:2736]
* - fix up 0.9 linksMike Bayer2013-05-294-5/+5
|
* - version 0.9Mike Bayer2013-05-294-4/+68
| | | | - changelog, migration doc
* changelogMike Bayer2013-05-291-0/+9
|
* Fixed a small bug in the dogpile example where the generationMike Bayer2013-05-281-0/+7
| | | | | of SQL cache keys wasn't applying deduping labels to the statement the same way :class:`.Query` normally does.
* Fixed a bug where the routine to detect the correct kwargsMike Bayer2013-05-231-0/+8
| | | | | | being sent to :func:`.create_engine` would fail in some cases, such as with the Sybase dialect. [ticket:2732]
* Regression from this ticket caused the unsupported keywordMike Bayer2013-05-151-0/+8
| | | | | | "true" to render, added logic to convert this to 1/0 for SQL server. [ticket:2682]
* Fixed a regression from 0.7 caused by this ticket, whichMike Bayer2013-05-131-0/+10
| | | | | | | | made the check for recursion overflow in self-referential eager joining too loose, missing a particular circumstance where a subclass had lazy="joined" or "subquery" configured and the load was a "with_polymorphic" against the base. [ticket:2481]
* - Fixed a regression from 0.7 where the contextmanager featureMike Bayer2013-04-301-0/+10
| | | | | | | of :meth:`.Session.begin_nested` would fail to correctly roll back the transaction when a flush error occurred, instead raising its own exception while leaving the session still pending a rollback. [ticket:2718]
* Updated mysqlconnector dialect to check for disconnect basedMike Bayer2013-04-291-0/+10
| | | | | on the apparent string message sent in the exception; tested against mysqlconnector 1.0.9.
* 0.8.1rel_0_8_1Mike Bayer2013-04-272-2/+3
|
* Fixes to the ``sqlalchemy.ext.serializer`` extension, includingMike Bayer2013-04-261-0/+10
| | | | | | | that the "id" passed from the pickler is turned into a string to prevent against bytes being parsed on Py3K, as well as that ``relationship()`` and ``orm.join()`` constructs are now properly serialized. [ticket:2698] and some other observed issues.
* changelog for [ticket:2714]Mike Bayer2013-04-261-0/+13
|
* - merge exists() patch + changelogMike Bayer2013-04-231-0/+8
|\
| * adding pullreq # to changelogDiana Clarke2013-03-291-0/+1
| |
| * adding convenience method exists() to Query (see # 2673)Diana Clarke2013-03-291-0/+7
| |
* | Added a conditional to the unpickling process for ORMMike Bayer2013-04-231-0/+9
| | | | | | | | | | | | | | mapped objects, such that if the reference to the object were lost when the object was pickled, we don't erroneously try to set up _sa_instance_state - fixes a NoneType error.
* | - only search in the exception before the first newline, to avoidMike Bayer2013-04-231-0/+1
| | | | | | | | false positives for SQL statements containing certain text
* | Opened up the checking for "disconnect" with psycopg2/libpqMike Bayer2013-04-221-0/+10
| | | | | | | | | | | | | | | | to check for all the various "disconnect" messages within the full exception hierarchy. Specifically the "closed the connection unexpectedly" message has now been seen in at least three different exception types. [ticket:2712]
* | Fully implemented the IS and IS NOT operators withMike Bayer2013-04-221-0/+12
| | | | | | | | | | | | | | | | | | | | regards to the True/False constants. An expression like ``col.is_(True)`` will now render ``col IS true`` on the target platform, rather than converting the True/ False constant to an integer bound parameter. This allows the ``is_()`` operator to work on MySQL when given True/False constants. [ticket:2682]
* | - change to [ticket:2681], pre-coerce the array to listMike Bayer2013-04-221-6/+3
| | | | | | | | unconditonally instead so that it works in all cases.
* | The operators for the Postgresql ARRAY type supportsMike Bayer2013-04-221-0/+12
| | | | | | | | | | | | | | | | | | | | input types of sets, generators, etc. but only when a dimension is specified for the ARRAY; otherwise, the dialect needs to peek inside of "arr[0]" to guess how many dimensions are in use. If this occurs with a non list/tuple type, the error message is now informative and directs to specify a dimension for the ARRAY. [ticket:2681]
* | - changelogMike Bayer2013-04-211-0/+7
| | | | | | | | - just do a fetchone() here, no need for len() etc.
View Lorry Controller Status