summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add basic LTREE support; missing testspr/187Renato Massaro2015-07-143-4/+73
|
* - Fixed bug in :class:`.AbstractConcreteBase` extension whereMike Bayer2015-07-134-2/+53
| | | | | | | | | a column setup on the ABC base which had a different attribute name vs. column name would not be correctly mapped on the final base class. The failure on 0.9 would be silent whereas on 1.0 it raised an ArgumentError, so may not have been noticed prior to 1.0. fixes #3480
* - try to note under insert.values(), if you needMike Bayer2015-07-082-4/+12
| | | | | | "multiple parameter sets" there is a much more common case which works equally well for INSERT/UPDATE/DELETE e.g. executemany(). reference #3476
* - add a warning suggesting to use the dictionary form of accessMike Bayer2015-07-051-0/+33
| | | | | | if the name of the attribute being accessed is non-specific, thereby avoiding collisions on names like items, values, keys. fixes #3475
* - fix the link here fixes 3473Mike Bayer2015-07-031-1/+1
|
* - increase the varchar hereMike Bayer2015-07-011-1/+1
|
* - Fixed 1.0 regression where value objects that overrideMike Bayer2015-07-013-2/+123
| | | | | | | | | ``__eq__()`` to return a non-boolean-capable object, such as some geoalchemy types as well as numpy types, were being tested for ``bool()`` during a unit of work update operation, where in 0.9 the return value of ``__eq__()`` was tested against "is True" to guard against this. fixes #3469
* - Fixed 1.0 regression where a "deferred" attribute would not populateMike Bayer2015-06-293-1/+78
| | | | | | | | | | correctly if it were loaded within the "optimized inheritance load", which is a special SELECT emitted in the case of joined table inheritance used to populate expired or unloaded attributes against a joined table without loading the base table. This is related to the fact that SQLA 1.0 no longer guesses about loading deferred columns and must be directed explicitly. fixes #3468
* - Fixed 1.0 regression where the "parent entity" of a synonym-Mike Bayer2015-06-277-4/+86
| | | | | | | | | | | | | mapped attribute on top of an :func:`.aliased` object would resolve to the original mapper, not the :func:`.aliased` version of it, thereby causing problems for a :class:`.Query` that relies on this attribute (e.g. it's the only representative attribute given in the constructor) to figure out the correct FROM clause for the query. fixes #3466 - apply consitency to ._parententity vs. __clause_element__()._annotations['parententity'] in terms of aliased class, test it all.
* Merge pull request #185 from megabyde/mastermike bayer2015-06-261-5/+4
|\ | | | | Fix code examples in automap's documentation
| * Fix code examples in automap's documentationpr/185Yuri Baida2015-06-261-5/+4
|/ | | Fix camelize_classname and pluralize_collection functions as they didn't work as expected.
* 1.0.6rel_1_0_6Mike Bayer2015-06-252-2/+3
|
* - add autoinc marker for oracleMike Bayer2015-06-251-2/+6
|
* - Fixed a major regression in the 1.0 series where the version_id_counterMike Bayer2015-06-243-1/+167
| | | | | | | | | | | | | feature would cause an object's version counter to be incremented when there was no net change to the object's row, but instead an object related to it via relationship (e.g. typically many-to-one) were associated or de-associated with it, resulting in an UPDATE statement that updates the object's version counter and nothing else. In the use case where the relatively recent "server side" and/or "programmatic/conditional" version counter feature were used (e.g. setting version_id_generator to False), the bug could cause an UPDATE without a valid SET clause to be emitted. fixes #3465
* - edits to this sectionMike Bayer2015-06-222-16/+20
|
* - add a new FAQ on re-reading of data within a transaction, sinceMike Bayer2015-06-222-3/+71
| | | | this is definitely something that is asked regularly.
* Merge pull request #184 from bnjmn/patch-1mike bayer2015-06-221-1/+1
|\ | | | | Missing comma in method params for hybrid docs
| * Missing comma in method argspr/184Benjamin Petersen2015-06-221-1/+1
|/
* - Fixed issue when using :class:`.VARBINARY` type in conjunction withMike Bayer2015-06-223-69/+123
| | | | | | | | | an INSERT of NULL + pyodbc; pyodbc requires a special object be passed in order to persist NULL. As the :class:`.VARBINARY` type is now usually the default for :class:`.LargeBinary` due to :ticket:`3039`, this issue is partially a regression in 1.0. The pymssql driver appears to be unaffected. fixes #3464
* - Re-fixed this issue first released in 1.0.5 to fix psycopg2cffiMike Bayer2015-06-222-1/+11
| | | | | | | | JSONB support once again, as they suddenly switched on unconditional decoding of JSONB types in version 2.7.1. Version detection now specifies 2.7.1 as where we should expect the DBAPI to do json encoding for us. fixes #3439
* Merge pull request #183 from renshawbay/mastermike bayer2015-06-221-1/+1
|\ | | | | Fix a tiny typo in test name
| * Fix typopr/183Pete Hollobon2015-06-221-1/+1
|/
* - repair that we use db_opts when the url here is different,Mike Bayer2015-06-191-3/+8
| | | | as we are using db_opts for the first time with legacy_schema_args
* - fixes to the warnings filtersMike Bayer2015-06-191-3/+1
|
* - more edits, references #3461Mike Bayer2015-06-192-18/+29
|
* - for #3455Mike Bayer2015-06-194-32/+75
| | | | | | | | | - changelog - versionadded + reflink for new pg storage parameters doc - pep8ing - add additional tests to definitely check that the Index object is created all the way with the opts we want fixes #3455
* Merge remote-tracking branch 'origin/pr/179' into pr179Mike Bayer2015-06-193-3/+99
|\
| * Add reflection of PostgreSQL index access methods (USING clause)pr/179Pete Hollobon2015-06-042-3/+32
| |
| * Add reflection of PostgreSQL index storage optionsPete Hollobon2015-06-042-3/+29
| |
| * Add support for PostgreSQL index storage parametersPete Hollobon2015-06-032-0/+41
| | | | | | | | | | Add support for specifying PostgreSQL index storage paramters (e.g. fillfactor).
* | - fix the bulletsMike Bayer2015-06-192-19/+26
| | | | | | | | | | | | - tone down the "never dispose an engine" language - refer to NullPool for the "I don't like pooling" use case references #3461
* | - Fixed 1.0 regression where the enhanced behavior of single-inheritanceMike Bayer2015-06-193-3/+39
| | | | | | | | | | | | | | | | joins of :ticket:`3222` takes place inappropriately for a JOIN along explicit join criteria with a single-inheritance subclass that does not make use of any discriminator, resulting in an additional "AND NULL" clause. fixes #3462
* | - add explciit section on engine disposal, fixes #3461Mike Bayer2015-06-192-14/+64
| |
* | - automap is stableMike Bayer2015-06-181-6/+0
| |
* | - Repaired the :class:`.ExcludeConstraint` construct to support commonMike Bayer2015-06-165-22/+108
| | | | | | | | | | | | | | features that other objects like :class:`.Index` now do, that the column expression may be specified as an arbitrary SQL expression such as :obj:`.cast` or :obj:`.text`. fixes #3454
* | - add a subsection on how to use Sequence with server_default,Mike Bayer2015-06-161-0/+40
| | | | | | | | fixes #3453
* | - remove the redundant non-max-row-buffer test from the max_row_bufferMike Bayer2015-06-141-12/+0
| | | | | | | | test as we implemented that as a separate test.
* | Merge branch 'pr182'Mike Bayer2015-06-149-61/+172
|\ \
| * | - add test cases for pullreq github:182, where we add a newMike Bayer2015-06-145-53/+155
| | | | | | | | | | | | | | | | | | | | | | | | "max_row_buffer" execution option for BufferedRowResultProxy - also add documentation, changelog and version notes - rework the max_row_buffer argument to be interpreted from the execution options upfront when the BufferedRowResultProxy is first initialized.
| * | - Add a new le_() assertion for less than or equalsMike Bayer2015-06-143-8/+14
| | | | | | | | | | | | | | | - fix TablesTest to use the bind that we've returned from setup_bind() to emit DELETE statements
| * | Added max_row_buffer attribute to the context execution options and usepr/182Morgan McClure2015-06-132-3/+9
| | | | | | | | | | | | it to prevent excess memory usage with yield_per
| * | BufferedRowResultProxy should stop growing at 100Morgan McClure2015-06-131-4/+1
| | |
* | | - revert this change which was inadvertently included in theMike Bayer2015-06-131-2/+1
| | | | | | | | | | | | fix for #3451
* | | - restore the approach we have for pk_params, but in orderMike Bayer2015-06-131-6/+8
| | | | | | | | | | | | | | | to suit #3451 exclude these columns from the "params" dictionary in the first place, revises pr github:181
* | | - add changelog for #3451, with 09485d733131b667813f44eb0b6807b698668ee7 ↵Mike Bayer2015-06-133-1/+33
| | | | | | | | | | | | | | | | | | fixes #3451 - also add a bulk_insert_mappings test
* | | Fix primary key behaviour in bulk_updatepr/181Patrick Hayes2015-06-132-10/+39
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Suppose you have a model class with a primary key. Base = declarative_base() class User(Base): id = Column(BigInteger, primary_key=True) name = Column(String) Previously, running `bulk_update_mappings(User, {'id': 1, 'name': 'hello'})` would emit the following: ```UPDATE users SET id=1, name='hello' WHERE id=1``` This is contrary to the stated behaviour, where primary keys are omitted from the SET clause. Furthermore, this behaviour is harmful, as it can cause the db engine to lock over-aggresively (at least in Postgres). With this change, the emitted SQL is: ```UPDATE users SET name='hello' WHERE id=1```
* | - Fixed an unexpected-use regression whereby custom :class:`.Comparator`Mike Bayer2015-06-115-2/+40
| | | | | | | | | | | | | | | | | | | | objects that made use of the ``__clause_element__()`` method and returned an object that was an ORM-mapped :class:`.InstrumentedAttribute` and not explicitly a :class:`.ColumnElement` would fail to be correctly handled when passed as an expression to :meth:`.Session.query`. The logic in 0.9 happened to succeed on this, so this use case is now supported. fixes #3448
* | - add an 0.9 migration note regarding TypeEngine's defaultMike Bayer2015-06-101-1/+65
| | | | | | | | constructor removal; fixes #3446
* | - Fixed a bug where clause adaption as applied to a :class:`.Label`Mike Bayer2015-06-093-1/+37
| | | | | | | | | | | | | | | | | | | | | | | | object would fail to accommodate the labeled SQL expression in all cases, such that any SQL operation that made use of :meth:`.Label.self_group` would use the original unadapted expression. One effect of this would be that an ORM :func:`.aliased` construct would not fully accommodate attributes mapped by :obj:`.column_property`, such that the un-aliased table could leak out when the property were used in some kinds of SQL comparisons. fixes #3445
* | - add a migration note for the query.update()/query.delete() changeMike Bayer2015-06-091-1/+15
| | | | | | | | in #3349
View Lorry Controller Status