summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | - rework ColumnAdapter and ORMAdapter to only provide the featuresticket_3148Mike Bayer2014-09-073-88/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | we're now using; rework them fully so that their behavioral contract is consistent regarding adapter.traverse() vs. adapter.columns[], add a full suite of tests including advanced wrapping scenarios previously only covered by test/orm/test_froms.py and test/orm/inheritance/test_relationships.py - identify several cases where label._order_by_label_clause would be corrupted, e.g. due to adaption or annotation separately - add full tests for #3148
* | | | - enhance ClauseAdapter / ColumnAdapter to have new behaviors with labels.Mike Bayer2014-09-076-30/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "anonymize label" logic is now generalized to ClauseAdapter, and takes place when the anonymize_labels flag is sent, taking effect for all .columns lookups as well as within traverse() calls against the label directly. - traverse() will also memoize what it gets in columns, so that calling upon traverse() / .columns against the same Label will produce the same anonymized label. This is so that AliasedClass produces the same anonymized label when it is accessed per-column (e.g. SomeAlias.some_column) as well as when it is applied to a Query, and within column loader strategies (e.g. query(SomeAlias)); the former uses traverse() while the latter uses .columns - AliasedClass now calls onto ColumnAdapter - Query also makes sure to use that same ColumnAdapter from the AliasedClass in all cases - update the logic from 0.9 in #1068 to make use of the same _label_resolve_dict we use for #2992, simplifying how that works and adding support for new scenarios that were pretty broken (see #3148, #3188)
* | | | wip for #3148Mike Bayer2014-09-066-14/+50
| | | |
* | | | - document all the varities of _label on the base ColumnElementMike Bayer2014-09-062-12/+56
| | | | | | | | | | | | | | | | | | | | - replace out _columns_clause_label with a straight boolean flag to reduce the proliferation of labels
* | | | - omit MySQL index flavor if its NoneMike Bayer2014-09-051-1/+2
| | | |
* | | | - MySQL boolean symbols "true", "false" work again. 0.9's changeMike Bayer2014-09-051-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in :ticket:`2682` disallowed the MySQL dialect from making use of the "true" and "false" symbols in the context of "IS" / "IS NOT", but MySQL supports this syntax even though it has no boolean type. MySQL remains "non native boolean", but the :func:`.true` and :func:`.false` symbols again produce the keywords "true" and "false", so that an expression like ``column.is_(true())`` again works on MySQL. fixes #3186
* | | | - tiny refactors #1-#5Mike Bayer2014-09-053-102/+130
| | | |
* | | | - ensure literal_binds works with LIMIT clause, FOR UPDATEMike Bayer2014-09-038-27/+42
| | | |
* | | | - The hostname-based connection format for SQL Server when usingMike Bayer2014-09-032-58/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | pyodbc will no longer specify a default "driver name", and a warning is emitted if this is missing. The optimal driver name for SQL Server changes frequently and is per-platform, so hostname based connections need to specify this. DSN-based connections are preferred. fixes #3182
* | | | - An adjustment to table/index reflection such that if an indexMike Bayer2014-09-021-8/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | reports a column that isn't found to be present in the table, a warning is emitted and the column is skipped. This can occur for some special system column situations as has been observed with Oracle. fixes #3180
* | | | - add logic to compiler such that if stack is empty, we justMike Bayer2014-09-023-2/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | stringify a _label_reference() as is. - add .key to _label_reference(), so that when _make_proxy() is called, we don't call str() on it anyway. - add a test to exercise Query's behavior of adding all the order_by expressions to the columns list of the select, assert that things work out when we have a _label_reference there, that it gets sucked into the columns list and spit out on the other side, it's referred to appropriately, etc. _label_reference() could theoretically be resolved at the point we iterate _raw_columns() but it's better to just let things work as they already do (except nicer, since we get "tablename.colname" instead of just "somename" in the columns list) so that we aren't adding a ton of overhead to _columns_plus_names in the common case.
* | | | - The :func:`~.expression.column` and :func:`~.expression.table`Mike Bayer2014-09-0111-55/+180
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | constructs are now importable from the "from sqlalchemy" namespace, just like every other Core construct. - The implicit conversion of strings to :func:`.text` constructs when passed to most builder methods of :func:`.select` as well as :class:`.Query` now emits a warning with just the plain string sent. The textual conversion still proceeds normally, however. The only method that accepts a string without a warning are the "label reference" methods like order_by(), group_by(); these functions will now at compile time attempt to resolve a single string argument to a column or label expression present in the selectable; if none is located, the expression still renders, but you get the warning again. The rationale here is that the implicit conversion from string to text is more unexpected than not these days, and it is better that the user send more direction to the Core / ORM when passing a raw string as to what direction should be taken. Core/ORM tutorials have been updated to go more in depth as to how text is handled. fixes #2992
* | | | - more updates to text docs, literal_column, column etc. in prepMike Bayer2014-09-011-9/+20
| | | | | | | | | | | | | | | | for ticket 2992.
* | | | - improve from_statement() docMike Bayer2014-08-311-3/+9
| | | |
* | | | - refine this a bit to better check for exception typeMike Bayer2014-08-311-7/+8
| | | |
* | | | - A new style of warning can be emitted which will "filter" up toMike Bayer2014-08-3112-130/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | N occurrences of a parameterized string. This allows parameterized warnings that can refer to their arguments to be delivered a fixed number of times until allowing Python warning filters to squelch them, and prevents memory from growing unbounded within Python's warning registries. fixes #3178
* | | | - alter the yield_per eager restriction such that joined many-to-one loadsMike Bayer2014-08-302-7/+16
| | | | | | | | | | | | | | | | are still OK, since these should be fine.
* | | | - continue moving things out that don't need to be thereMike Bayer2014-08-301-68/+59
| | | | | | | | | | | | | | | | | | | | | | | | - an existing state shouldn't need its load_options/load_path updated; it should maintain those from its original Query source. there's no tests that check this behavior
* | | | - clean up zoomark a little and try to get new profiles writtenMike Bayer2014-08-301-5/+10
| | | |
* | | | - do the polymorphic thing as a decorator so it's out of the way otherwiseMike Bayer2014-08-291-31/+22
| | | |
* | | | - pull out populators back into separate functions, though still very inlinedMike Bayer2014-08-291-82/+114
| | | |
* | | | - further move things vertically, at which point things are inlined enoughMike Bayer2014-08-291-51/+60
| | | | | | | | | | | | | | | | that I'd like to start de-inlining again in the hopes of making this readable.
* | | | - need to use safe_discard() at least in _restore_snapshot(), let's use itMike Bayer2014-08-291-3/+3
| | | | | | | | | | | | | | | | everywhere in Session since the optimized one only applies to loading
* | | | - defaultdict benchmarks faster than a namedtuple; OKMike Bayer2014-08-293-107/+104
| | | | | | | | | | | | | | | | - inline the column-based expiration operations as well
* | | | - reorganize how create_row_processor() communicates up toMike Bayer2014-08-293-82/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | instances(), using a named tuple it can assign to directly. this way we never have to worry about that structure changing anymore, though we are still having it append (key, fn) which is kind of awkward. - inline _populators() into instance(), it's a little verbose but saves an fn call
* | | | - re-establish and test some behavior from previous versions, thatMike Bayer2014-08-291-11/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | if a load() or refresh() event changes history (which...why...but anyway) the state of the object is the same; currently it seems that history gets reset but on a refresh, the object still goes into session.dirty - simplify what we store in partials
* | | | - The :class:`.Query` will raise an exception when :meth:`.Query.yield_per`Mike Bayer2014-08-292-3/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | is used with mappings or options where eager loading, either joined or subquery, would take place. These loading strategies are not currently compatible with yield_per, so by raising this error, the method is safer to use - combine with sending False to :meth:`.Query.enable_eagerloads` to disable the eager loaders.
* | | | - add some more docs to yield_perMike Bayer2014-08-291-18/+38
| | | |
* | | | - use a faster discard when loadingMike Bayer2014-08-293-4/+16
| | | | | | | | | | | | | | | | - don't do a bool on identity map since it calls __len__
* | | | - inline the commit of partials tooMike Bayer2014-08-291-3/+3
| | | |
* | | | - Changed the approach by which the "single inheritance criterion"Mike Bayer2014-08-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | is applied, when using :meth:`.Query.from_self`, or its common user :meth:`.Query.count`. The criteria to limit rows to those with a certain type is now indicated on the inside subquery, not the outside one, so that even if the "type" column is not available in the columns clause, we can filter on it on the "inner" query. fixes #3177
* | | | inlines galoreMike Bayer2014-08-291-34/+32
| | | |
* | | | - major refactoring/inlining to loader.instances(), though not reallyMike Bayer2014-08-2812-458/+188
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | any speed improvements :(. code is in a much better place to be run into C, however - The ``proc()`` callable passed to the ``create_row_processor()`` method of custom :class:`.Bundle` classes now accepts only a single "row" argument. - Deprecated event hooks removed: ``populate_instance``, ``create_instance``, ``translate_row``, ``append_result`` - the getter() idea is somewhat restored; see ref #3175
* | | | - Made a small adjustment to the mechanics of lazy loading,Mike Bayer2014-08-282-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | such that it has less chance of interfering with a joinload() in the very rare circumstance that an object points to itself; in this scenario, the object refers to itself while loading its attributes which can cause a mixup between loaders. The use case of "object points to itself" is not fully supported, but the fix also removes some overhead so for now is part of testing. fixes #3145
* | | | - this is small optimization, currently it's the best we can doMike Bayer2014-08-281-1/+2
| | | | | | | | | | | | | | | | for #3175. fixes #3175 (for now)
* | | | - A new implementation for :class:`.KeyedTuple` used by theMike Bayer2014-08-284-21/+66
| | | | | | | | | | | | | | | | | | | | | | | | :class:`.Query` object offers dramatic speed improvements when fetching large numbers of column-oriented rows. fixes #3176
* | | | - The behavior of :paramref:`.joinedload.innerjoin` as well asMike Bayer2014-08-263-20/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | :paramref:`.relationship.innerjoin` is now to use "nested" inner joins, that is, right-nested, as the default behavior when an inner join joined eager load is chained to an outer join eager load. fixes #3008
* | | | - updates to migration / changelog for 1.0Mike Bayer2014-08-261-1/+1
| |_|/ |/| |
* | | Merge branch 'mutable-dict-update' of ↵Mike Bayer2014-08-251-0/+4
|\ \ \ | | | | | | | | | | | | https://bitbucket.org/goodscloud/sqlalchemy into pr27
| * | | add update() support to MutableDictMatt Chisholm2014-08-091-0/+4
| | | |
* | | | Merge branch 'mutable-dict-coerce-fix' of ↵Mike Bayer2014-08-251-3/+3
|\ \ \ \ | | | | | | | | | | | | | | | https://bitbucket.org/goodscloud/sqlalchemy into pr27
| * | | | fix MutableDict.coerceMatt Chisholm2014-08-091-3/+3
| |/ / / | | | | | | | | | | | | If a class inherited from MutableDict (say, for instance, to add an update() method), coerce() would give back an instance of MutableDict instead of an instance of the derived class.
* | | | - mention that FOUND_ROWS is hardcoded; fixes #3146Mike Bayer2014-08-251-7/+5
| | | |
* | | | - The "resurrect" ORM event has been removed. This event hook hadMike Bayer2014-08-252-23/+0
| | | | | | | | | | | | | | | | | | | | | | | | no purpose since the old "mutable attribute" system was removed in 0.8. fixes #3171
* | | | Merge branch 'pr129'Mike Bayer2014-08-231-1/+71
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Conflicts: doc/build/changelog/changelog_10.rst
| * | | | - pep8 formatting for pg table opts feature, testsMike Bayer2014-08-231-24/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add support for PG INHERITS - fix mis-named tests - changelog fixes #2051
| * | | | Adding postgres create table options documentationpr/129Malik Diarra2014-08-171-0/+16
| | | | |
| * | | | Correcting options name from withoids to with_oidsMalik Diarra2014-08-171-3/+3
| | | | |
| * | | | quoting tablespace name in create table command in postgresql dialectMalik Diarra2014-08-171-1/+2
| | | | |
| * | | | Adding oids and on_commit table optionsMalik Diarra2014-08-171-1/+11
| | | | |
View Lorry Controller Status