summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add Query.one_or_none()pr/201Eric Siegerman2015-09-244-1/+96
|
* Add a lot more detailEric Siegerman2015-09-231-3/+22
| | | | (cherry picked from commit 5db5e18d3babdb3ee857c075c774a585505b78ce)
* Add some markupEric Siegerman2015-09-231-2/+2
| | | | (cherry picked from commit 81eefe038ea44a5314002483dde9cf00580df1bd)
* A few minor rewordingsEric Siegerman2015-09-231-3/+3
| | | | (cherry picked from commit ea084bdc656a6a64db1ee582630d415bc8154505)
* - Fixed rare TypeError which could occur when stringifying certainMike Bayer2015-09-233-2/+20
| | | | | kinds of internal column loader options within internal logging. fixes #3539
* - The ``legacy_schema_aliasing`` flag, introduced in version 1.0.5Mike Bayer2015-09-196-79/+96
| | | | | | | 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-197-11/+259
| | | | | | | | | | | | | 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-194-1/+91
| | | | | | | 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-1610-65/+373
| | | | | | | | | | | 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
* - fix incorrect example in inheritance docsMike Bayer2015-09-151-3/+3
|
* - add new entry for sharing of Engine across process boundariesMike Bayer2015-09-141-0/+81
|
* - call it deque, since you can really pop from either sideMike Bayer2015-09-101-5/+5
|
* - add a new FAQ recipe for "walk all objects", replacing the needMike Bayer2015-09-102-4/+84
| | | | | | to use mapper.cascade_iterator() for this purpose as it was not really designed for that use case. Add docs to cascade_iterator() pointing to the recipe. fixes #3498
* Correcting the Hybrid Property ExampleJason Myers2015-09-101-1/+1
| | | | | | Fixes #3528 Signed-off-by: Jason Myers <jason@jasonamyers.com>
* - profile updateMike Bayer2015-09-081-1/+1
|
* Merged in bsmithgall/sqlalchemy/event-doc-link-fix (pull request #60)Mike Bayer2015-09-081-1/+1
|\ | | | | | | fix typo in session events docs
| * fix typo in session events docsbsmithgall2015-09-071-1/+1
| |
* | Merge pull request #197 from davidjb/mastermike bayer2015-09-081-1/+1
|\ \ | | | | | | Minor grammar fix for capitalisation in session docs
| * | Minor grammar fix for capitalisation in session docspr/197David\ Beitey2015-08-281-1/+1
| | |
* | | - Internal calls to "bookkeeping" functions withinMike Bayer2015-09-083-50/+69
| | | | | | | | | | | | | | | | | | | | | | | | :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-083-2/+70
| |/ |/| | | | | | | | | | | 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
* | - update moved link, fixes #3351Mike Bayer2015-09-031-1/+1
| |
* | - rewrite some profiles that went *down*! woopMike Bayer2015-09-031-5/+5
| |
* | - reduce some callcounts within the new eventsMike Bayer2015-09-032-32/+30
| |
* | Merge branch 'ticket_2677'Mike Bayer2015-09-0222-382/+1910
|\ \
| * | - The :class:`.SessionEvents` suite now includes events to allowticket_2677Mike Bayer2015-09-0217-247/+1593
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | - add new documentation that applies to all modern SQLA versions,ticket_2677_preMike Bayer2015-09-028-157/+339
| | | | | | | | | | | | detailing ORM event recipes across the board.
* | | - add a note about DISTINCT in query w/ ORDER BY, references #3518Mike Bayer2015-08-311-0/+13
| | |
* | | - Fixed regression in 1.0-released default-processor for multi-VALUESMike Bayer2015-08-314-16/+64
|/ / | | | | | | | | | | | | | | 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
* | - use consistent and descriptive language in all casesMike Bayer2015-08-273-9/+52
|/ | | | | | where we refer to the "weak_identity_map" option, and add additional exposition in the session documentation which refers to it. fixes #3517
* - The :class:`.TypeDecorator` type extender will now work in conjunctionMike Bayer2015-08-275-9/+90
| | | | | | | | | | | with a :class:`.SchemaType` implementation, typically :class:`.Enum` or :class:`.Boolean` with regards to ensuring that the per-table events are propagated from the implementation type to the outer type. These events are used to ensure that the constraints or Postgresql types (e.g. ENUM) are correctly created (and possibly dropped) along with the parent table. fixes #2919
* - reword and update documentation on passive_updates=False; as virtuallyMike Bayer2015-08-272-56/+104
| | | | | | | all DBs now support ON UPDATE CASCADE other than Oracle, there's no need to try to reimplement more functionality here and users should be encouraged to forego natural PKs unless their target platform supports them. references #2666
* - add a postgresql-specific form of array_agg() that injects theMike Bayer2015-08-279-8/+56
| | | | ARRAY type, references #3132
* - consolidate "constraints.py" into the more general "ext.py",Mike Bayer2015-08-273-100/+92
| | | | for all assorted PG SQL extensions
* - add PG-specific aggregate_order_by(), references #3132Mike Bayer2015-08-277-3/+132
|
* Merge branch 'ticket_3516'Mike Bayer2015-08-2626-259/+1458
|\
| * - Added support for "set-aggregate" functions of the formticket_3516Mike Bayer2015-08-2612-49/+477
| | | | | | | | | | | | | | | | | | | | | | ``<function> WITHIN GROUP (ORDER BY <criteria>)``, using the method :class:`.FunctionElement.within_group`. A series of common set-aggregate functions with return types derived from the set have been added. This includes functions like :class:`.percentile_cont`, :class:`.dense_rank` and others. fixes #1370 - make sure we use func.name for all _literal_as_binds in functions.py so we get consistent naming behavior for parameters.
| * - Added support for the SQL-standard function :class:`.array_agg`,Mike Bayer2015-08-264-2/+69
| | | | | | | | | | | | | | which automatically returns an :class:`.Array` of the correct type and supports index / slice operations. As arrays are only supported on Postgresql at the moment, only actually works on Postgresql. fixes #3132
| * - build out a new base type for Array, as well as new any/all operatorsMike Bayer2015-08-2522-214/+918
| | | | | | | | | | | | - any/all work for Array as well as subqueries, accepted by MySQL - Postgresql ARRAY now subclasses Array - fixes #3516
* | - re-document and fully cross link all of configure_mappers(),Mike Bayer2015-08-242-20/+111
|/ | | | mapper_configured(), after_configured(), and before_configured().
* - Fixed two issues in the "history_meta" example where history trackingMike Bayer2015-08-243-4/+78
| | | | | | could encounter empty history, and where a column keyed to an alternate attribute name would fail to track properly. Fixes courtesy Alex Fraser.
* - repair the inspection hook in sqltypes to not be fooledMike Bayer2015-08-223-2/+17
| | | | by mock and other __getattr__ impostors
* - Added new checks for the common error case of passing mapped classesMike Bayer2015-08-2211-15/+139
| | | | | | or mapped instances into contexts where they are interpreted as SQL bound parameters; a new exception is raised for this. fixes #3321
* - rework the "controlling DDL sequences" documentation toMike Bayer2015-08-211-116/+124
| | | | | | refer mostly to the DDL object; this system is primarily useful in that case, and not for built-in objects. Reference that the built-in case is not really viable right now. References #3442.
* - some cleanups in compiler.pyMike Bayer2015-08-181-50/+32
|
* - forgot to implement py3k logic for JSON.NULLMike Bayer2015-08-181-23/+21
|
* - fix the postgresql_jsonb requirement to include the 9.4 requirementMike Bayer2015-08-184-8/+8
| | | | | | | | - new test for json col['x']['y']['z'] seems to fail pre PG 9.4, fails on comparisons for non-compatible data instead of not matching - no need to call SpecPredicate(db) directly in exclusion functions, by using Predicate.as_predicate() the spec strings can have version comparisons
* - as the Concatenable mixin was changed to support calling down toMike Bayer2015-08-183-3/+60
| | | | | | | | | | | | "super" instead of hardcoding to "self.type" for the default return value, the base Comparator was returning other_comparator.type. It's not clear what the rationale for this was, though in theory the base Comparator should possibly even throw an exception if the two types aren't the same (or of the same affinity?) . - mysql.SET was broken on this because the bitwise version adds "0" to the value to force an integer within column_expression, we are doing type_coerces here now in any case so that there is no type ambiguity for this operation
* - document workaround type for ARRAY of ENUM, fixes #3467Mike Bayer2015-08-182-0/+45
|
View Lorry Controller Status