summaryrefslogtreecommitdiff
path: root/doc/build/faq
Commit message (Collapse)AuthorAgeFilesLines
* Remove LRU warningsMike Bayer2017-09-081-50/+0
| | | | | | | | | | | | | | | Removed the warnings that are emitted when the LRU caches employed by the mapper as well as loader srtategies reach their threshold; the purpose of this warning was at first a guard against excess cache keys being generated but became basically a check on the "creating many engines" antipattern. While this is still an antipattern, the presense of test suites which both create an engine per test as well as raise on all warnings will be an inconvenience; it should not be critical that such test suites change their architecture just for this warning (though engine-per-test suite is always better). Change-Id: I41ef8cd642d05a845f53119b196440f9d7879cd9 Fixes: #4071
* - fix typosMike Bayer2017-08-221-1/+5
| | | | Change-Id: Ibf8bc0e997ff989c7b0c16afad48a95414078052
* - modernize the mysql connection timeout docsMike Bayer2017-08-221-12/+16
| | | | | Change-Id: Icb0474509539c1eb7536544749f2a48b4972078a (cherry picked from commit 4ce46fb0a085c1cc739e21881cc25567e663f8dc)
* Add all versioning logic to _post_update()Mike Bayer2017-06-151-1/+29
| | | | | | | | | | An UPDATE emitted as a result of the :paramref:`.relationship.post_update` feature will now integrate with the versioning feature to both bump the version id of the row as well as assert that the existing version number was matched. Fixes: #3496 Change-Id: I865405dd6069f1c1e3b0d27a4980e9374e059f97
* Repair formatting throughout documentationKataev Denis2017-05-227-24/+24
| | | | | | | | | | | 1. Section decorators to [one style](http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#sections): without inset at both side and with same length as text. 2. Fix broken [reference](http://docs.sqlalchemy.org/en/latest/core/type_basics.html#generic-types). 3. Convert tabs to space in some small files. 4. Some python code snippets have python+sql syntax hint. Change-Id: I39a7a41ef0b0591c6bf1e610748e2b5c19fc5379 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/361
* Add selectin loadingMike Bayer2017-04-261-1/+3
| | | | | | | | | | Adding a new kind of relationship loader that is a cross between the "immediateload" and the "subquery" eager loader, using an IN criteria to load related items in bulk immediately after the lead query result is loaded. Change-Id: If13713fba9b465865aef8fd50b5b6b977fe3ef7d Fixes: #3944
* - update relationship loader docs, backport fromMike Bayer2017-04-211-3/+3
| | | | | | 1.2 wip Change-Id: I0a3c4a0166f6feed23a021723233d281fad597ec
* - typos and formattingMike Bayer2017-04-121-3/+3
| | | | Change-Id: I88a304e315b68eded31e91da04265da583bc417b
* Warn on _compiled_cache growthMike Bayer2017-04-121-0/+51
| | | | | | | | | | | | | | | | | Added warnings to the LRU "compiled cache" used by the :class:`.Mapper` (and ultimately will be for other ORM-based LRU caches) such that when the cache starts hitting its size limits, the application will emit a warning that this is a performance-degrading situation that may require attention. The LRU caches can reach their size limits primarily if an application is making use of an unbounded number of :class:`.Engine` objects, which is an antipattern. Otherwise, this may suggest an issue that should be brought to the SQLAlchemy developer's attention. Additionally, adjusted the test_memusage algorithm again as the previous one could still allow a growing memory size to be missed. Change-Id: I020d1ceafb7a08f6addfa990a1e7acd09f933240
* Docs/faq/performanceIhor Kalnytskyi2017-03-301-13/+31
| | | | | | | | | | | | Some updates for FAQ/Performance documentation page: * Fix typo in testing script. * Populate testing script with one more way to achieve higher performance. See commit messages for details. Change-Id: Id6fbf328164b14b3b58ca9616b103a35e72f7b8f Pull-request: https://github.com/zzzeek/sqlalchemy/pull/345
* Add "empty in" strategies; default to "static"Mike Bayer2017-03-141-50/+0
| | | | | | | | | | | | | | | The longstanding behavior of the :meth:`.Operators.in_` and :meth:`.Operators.not_in_` operators emitting a warning when the right-hand condition is an empty sequence has been revised; a new flag :paramref:`.create_engine.empty_in_strategy` allows an empty "IN" expression to generate a simple boolean expression, or to invoke the previous behavior of dis-equating the expression to itself, with or without a warning. The default behavior is now to emit the simple boolean expression, allowing an empty IN to be evaulated without any performance penalty. Change-Id: I65cc37f2d7cf65a59bf217136c42fee446929352 Fixes: #3907
* spelling: Postgresql -> PostgreSQLVille Skyttä2016-10-081-1/+1
|
* Fix typopr/296Jeff Widman2016-07-251-1/+1
|
* Spelling fixes: "the a"Ville Skyttä2016-05-051-1/+1
|
* Merge remote-tracking branch 'origin/pr/268'Mike Bayer2016-05-043-8/+8
|\
| * Adds parentheses around print statements in docs.pr/268Jeffrey Finkelstein2016-05-033-8/+8
| |
* | Corrects some references in ORM documentation.pr/267Jeffrey Finkelstein2016-05-031-1/+2
|/
* - fix broken link to loader behaviorMike Bayer2015-11-071-1/+1
|
* - 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-101-0/+71
| | | | | | 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
* - edits to this sectionMike Bayer2015-06-221-15/+19
|
* - add a new FAQ on re-reading of data within a transaction, sinceMike Bayer2015-06-221-0/+62
| | | | this is definitely something that is asked regularly.
* - squash-merge the improve_toc branch, which moves all the Sphinx stylingMike Bayer2014-12-177-0/+1539
and extensions into an external library, and also reorganizes most large documentation pages into many small areas to reduce scrolling and better present the context into a more fine-grained hierarchy.
View Lorry Controller Status