summaryrefslogtreecommitdiff
path: root/test/aaa_profiling
Commit message (Collapse)AuthorAgeFilesLines
...
* - a new approach to profiling where we attempt to strip outMike Bayer2012-08-096-102/+48
| | | | | | parts of the pstats that are idiosyncratic to different platforms. the goal is no per-version assertions on tests, version differences in theory would go into the list of profiling exceptions.
* - fixesMike Bayer2012-08-071-1/+1
|
* -whitespace bonanza, contdMike Bayer2012-07-282-6/+6
|
* trailing whitespace bonanzaMike Bayer2012-07-281-4/+4
|
* - some more interpret_as_fromsMike Bayer2012-07-231-8/+8
|
* callcounts due to more engine event logicMike Bayer2012-07-191-4/+2
|
* try to get these to pass on jenkinsMike Bayer2012-07-171-2/+2
|
* relax this variance for nowMike Bayer2012-07-171-2/+2
|
* some test fixes and cleanupMike Bayer2012-07-161-17/+17
|
* move mapper-level UOW functionality straight into unitofwork also. there'sMike Bayer2012-07-141-2/+2
| | | | | | no need for this to be per-mapper. can't move dependency init off of property though as this init needs to happen up front, added a test to prove it.
* turn commit_all into an iterative methodMike Bayer2012-06-251-1/+1
|
* - somehting is making this test have an inconsistent callcountMike Bayer2012-06-241-1/+1
|
* callcounts, due to the DummyLock cleanupMike Bayer2012-06-231-3/+3
|
* a likely callcountMike Bayer2012-06-211-1/+6
|
* callcountMike Bayer2012-06-201-2/+1
|
* - [feature] The of_type() construct on attributesMike Bayer2012-06-201-46/+112
| | | | | | | | | | | | | | | | | | | | | | | | now accepts aliased() class constructs as well as with_polymorphic constructs, and works with query.join(), any(), has(), and also eager loaders subqueryload(), joinedload(), contains_eager() [ticket:2438] [ticket:1106] - a rewrite of the query path system to use an object based approach for more succinct usage. the system has been designed carefully to not add an excessive method overhead. - [feature] select() features a correlate_except() method, auto correlates all selectables except those passed. Is needed here for the updated any()/has() functionality. - remove some old cruft from LoaderStrategy, init(),debug_callable() - use a namedtuple for _extended_entity_info. This method should become standard within the orm internals - some tweaks to the memory profile tests, number of runs can be customized to work around pysqlite's very annoying behavior - try to simplify PropertyOption._get_paths(), rename to _process_paths(), returns a single list now. overall works more completely as was needed for of_type() functionality
* obnoxious callcountsMike Bayer2012-06-161-1/+1
|
* callcount fixMike Bayer2012-06-131-1/+2
|
* weird, seems like hasattr() doesn't count as a function call in the same way ↵Mike Bayer2012-06-121-1/+1
| | | | as isinstance()...
* - [bug] Fixed bug affecting Py3K wherebyMike Bayer2012-06-111-2/+1
| | | | | | | | string positional parameters passed to engine/connection execute() would fail to be interpreted correctly, due to __iter__ being present on Py3K string. [ticket:2503]. Also in 0.7.8.
* callcountMike Bayer2012-06-111-1/+1
|
* make sure integer is here. only the C ext doesn't try to call ↵Mike Bayer2012-06-111-0/+1
| | | | | | "key_fallback" for integer here, pure python one does.
* callcount adjustMike Bayer2012-06-081-1/+1
|
* - [bug] Fixed memory leak in C version ofMike Bayer2012-06-011-0/+57
| | | | | | | | result proxy whereby DBAPIs which don't deliver pure Python tuples for result rows would fail to decrement refcounts correctly. The most prominently affected DBAPI is pyodbc. [ticket:2489]
* callcount bump to work around sqlite's silly column name workaroundMike Bayer2012-05-041-4/+4
|
* callcountMike Bayer2012-04-241-1/+1
|
* py3k fixesMike Bayer2012-04-241-2/+2
|
* - [feature] Calling rollback() within aMike Bayer2012-04-241-2/+2
| | | | | | | | | | | | | | session.begin_nested() will now only expire those objects that had net changes within the scope of that transaction, that is objects which were dirty or were modified on a flush. This allows the typical use case for begin_nested(), that of altering a small subset of objects, to leave in place the data from the larger enclosing set of objects that weren't modified in that sub-transaction. [ticket:2452] - inline the "register_newly_XYZ" functions to operate upon collections to reduce method calls
* - [feature] The behavior of column targetingMike Bayer2012-04-242-6/+6
| | | | | | | | | | | | | | in result sets is now case sensitive by default. SQLAlchemy for many years would run a case-insensitive conversion on these values, probably to alleviate early case sensitivity issues with dialects like Oracle and Firebird. These issues have been more cleanly solved in more modern versions so the performance hit of calling lower() on identifiers is removed. The case insensitive comparisons can be re-enabled by setting "case_insensitive=False" on create_engine(). [ticket:2423]
* callcount tweak here, this moved up due to r5b6237e3f068Mike Bayer2012-04-241-2/+1
|
* - [removed] The legacy "mutable" system of theMike Bayer2012-04-231-48/+0
| | | | | | | | | | | | | | ORM, including the MutableType class as well as the mutable=True flag on PickleType and postgresql.ARRAY has been removed. In-place mutations are detected by the ORM using the sqlalchemy.ext.mutable extension, introduced in 0.7. The removal of MutableType and associated constructs removes a great deal of complexity from SQLAlchemy's internals. The approach performed poorly as it would incur a scan of the full contents of the Session when in use. [ticket:2442]
* the callcounts are greater here since object_mapper() has a little more ↵Mike Bayer2012-04-231-1/+1
| | | | overhead to it now
* - some adjustments to keep hybrid properties workingMike Bayer2012-04-231-1/+1
| | | | - callcount here seems to have gone up by five, reason not certain
* - merged #1401 branch from bitbucketMike Bayer2012-04-221-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - resolved some serious speed hits I missed, we need to ensure only deannotated columns are used in the local/remote collections and soforth so that hash lookups against mapped columns don't dig into __eq__() - fix some other parity mismatches regarding stuff from [ticket:2453], including finding another case where _deep_annotate() was doing the wrong thing, new tests. - [feature] Major rewrite of relationship() internals now allow join conditions which include columns pointing to themselves within composite foreign keys. A new API for very specialized primaryjoin conditions is added, allowing conditions based on SQL functions, CAST, etc. to be handled by placing the annotation functions remote() and foreign() inline within the expression when necessary. Previous recipes using the semi-private _local_remote_pairs approach can be upgraded to this new approach. [ticket:1401]
* | callcounts for py3kMike Bayer2012-03-142-3/+4
| |
* | callcountsMike Bayer2012-03-141-2/+2
| |
* | - [bug] Fixed memory leak in core which wouldMike Bayer2012-03-101-0/+16
| | | | | | | | | | | | | | occur when C extensions were used with particular types of result fetches, in particular when orm query.count() were called. [ticket:2427]
* | callcount tweakMike Bayer2012-03-051-1/+1
| |
* | fix callcountMike Bayer2012-02-261-1/+1
| |
* | callcountsMike Bayer2012-02-151-2/+2
| |
* | test failuresMike Bayer2012-02-151-4/+4
|/
* callcount adjustMike Bayer2012-02-051-2/+2
|
* - [bug] A significant change to how labelingMike Bayer2012-02-051-1/+1
| | | | | | | | | | | | | | is applied to columns in SELECT statements allows "truncated" labels, that is label names that are generated in Python which exceed the maximum identifier length (note this is configurable via label_length on create_engine()), to be properly referenced when rendered inside of a subquery, as well as to be present in a result set row using their original in-Python names. [ticket:2396] - apply pep8 to test_labels
* callcountMike Bayer2011-12-071-2/+2
|
* some call count reductionMike Bayer2011-12-031-1/+1
|
* - [bug] Fixed bug whereby column_property() createdMike Bayer2011-12-033-47/+54
| | | | | | | | | | | | | | | | | | | | | | | | | against ORM-level column could be treated as a distinct entity when producing certain kinds of joined-inh joins. [ticket:2316] - [bug] related to [ticket:2316], made some adjustments to the change from [ticket:2261] regarding the "from" list on a select(). The _froms collection is no longer memoized, as this simplifies various use cases and removes the need for a "warning" if a column is attached to a table after it was already used in an expression - the select() construct will now always produce the correct expression. There's probably no real-world performance hit here; select() objects are almost always made ad-hoc, and systems that wish to optimize the re-use of a select() would be using the "compiled_cache" feature. A hit which would occur when calling select.bind has been reduced, but the vast majority of users shouldn't be using "bound metadata" anyway :).
* fixes to actually get tests to passMike Bayer2011-11-221-2/+2
|
* minor callcount bump resulting from r3876c9c0b9a4Mike Bayer2011-09-092-3/+3
|
* - Added a slightly nicer __repr__() to SchemaItemMike Bayer2011-08-141-0/+2
| | | | | | | | classes. Note the repr here can't fully support the "repr is the constructor" idea since schema items can be very deeply nested/cyclical, have late initialization of some things, etc. [ticket:2223]
* - add test profiling merge() behavior when merging lots of bidirectional ↵Mike Bayer2011-08-121-0/+75
| | | | | | | | collections/m2os, collections present in given merge field. This shows that the change proposed in [ticket:2221] adds over 10% method call overhead including significantly more SQL statements.
View Lorry Controller Status