summaryrefslogtreecommitdiff
path: root/examples
Commit message (Collapse)AuthorAgeFilesLines
* - Added a new extension suite :mod:`sqlalchemy.ext.baked`. ThisMike Bayer2015-03-112-1/+26
| | | | | | | | simple but unusual system allows for a dramatic savings in Python overhead for the construction and processing of orm :class:`.Query` objects, from query construction up through rendering of a string SQL statement. fixes #3054
* - add a callers optionMike Bayer2015-03-091-1/+7
|
* - pick around gaining modest dings in callcounts here and thereMike Bayer2015-03-091-1/+1
|
* - random performance whacking vs. 0.9, in particular we have to watchMike Bayer2015-03-083-10/+12
| | | | for the slots-based __getattr__ thing getting hit
* - add this for testingMike Bayer2015-03-081-0/+109
|
* Maul the evaulate & friends typoPriit Laes2014-12-191-1/+1
|
* - A new series of :class:`.Session` methods which provide hooksMike Bayer2014-12-082-0/+11
| | | | | | | | | | directly into the unit of work's facility for emitting INSERT and UPDATE statements has been created. When used correctly, this expert-oriented system can allow ORM-mappings to be used to generate bulk insert and update statements batched into executemany groups, allowing the statements to proceed at speeds that rival direct use of the Core. fixes #3100
* Merge branch 'master' into ticket_3100Mike Bayer2014-12-073-74/+204
|\
| * - Updated the :ref:`examples_versioned_history` example such thatMike Bayer2014-11-262-21/+97
| | | | | | | | | | | | | | | | | | | | mapped columns are re-mapped to match column names as well as grouping of columns; in particular, this allows columns that are explicitly grouped in a same-column-named joined inheritance scenario to be mapped in the same way in the history mappings, avoiding warnings added in the 0.9 series regarding this pattern and allowing the same view of attribute keys.
| * - formattingMike Bayer2014-11-262-53/+106
| |
| * - Fixed a bug in the ↵Mike Bayer2014-11-241-0/+1
| | | | | | | | | | | | | | | | examples/generic_assocaitions/discriminator_on_association.py example, where the subclasses of AddressAssociation were not being mapped as "single table inheritance", leading to problems when trying to use the mappings further.
* | bulk_updatesMike Bayer2014-11-061-0/+54
| |
* | - add differentiating examples of list() vs. iterationMike Bayer2014-09-161-4/+10
| |
* | - try to finish up the performance example for nowMike Bayer2014-09-065-44/+284
| |
* | - add a test that shows query caching.Mike Bayer2014-09-041-0/+19
| |
* | tweakMike Bayer2014-09-032-6/+9
| |
* | refineMike Bayer2014-09-031-23/+43
| |
* | Merge branch 'master' into ticket_3100Mike Bayer2014-09-031-2/+0
|\ \ | |/
* | - large resultsetsMike Bayer2014-09-034-20/+337
| |
* | - wipMike Bayer2014-09-032-27/+194
| |
* | - lets start exampling this stuffMike Bayer2014-09-022-0/+148
|/
* Materialized paths example.Jack Zhou2014-06-072-0/+131
|
* Fix many typos throughout the codebasepr/85Alex Gaynor2014-04-262-3/+3
| | | | Found using: https://github.com/intgr/topy
* - Support has been added for pytest to run tests. This runnerMike Bayer2014-03-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | is currently being supported in addition to nose, and will likely be preferred to nose going forward. The nose plugin system used by SQLAlchemy has been split out so that it works under pytest as well. There are no plans to drop support for nose at the moment and we hope that the test suite itself can continue to remain as agnostic of testing platform as possible. See the file README.unittests.rst for updated information on running tests with pytest. The test plugin system has also been enhanced to support running tests against mutiple database URLs at once, by specifying the ``--db`` and/or ``--dburi`` flags multiple times. This does not run the entire test suite for each database, but instead allows test cases that are specific to certain backends make use of that backend as the test is run. When using pytest as the test runner, the system will also run specific test suites multiple times, once for each database, particularly those tests within the "dialect suite". The plan is that the enhanced system will also be used by Alembic, and allow Alembic to run migration operation tests against multiple backends in one run, including third-party backends not included within Alembic itself. Third party dialects and extensions are also encouraged to standardize on SQLAlchemy's test suite as a basis; see the file README.dialects.rst for background on building out from SQLAlchemy's test platform.
* - Fixed bug in the versioned_history example where column-level INSERTMike Bayer2014-02-242-5/+38
| | | | defaults would prevent history values of NULL from being written.
* - use column.info to detect those cols part of "versioning"Mike Bayer2014-02-162-28/+56
| | | | | | | - pep8 cleanup - fix tests for "changed" column - document that "changed" is optional - changelog
* Merge branch 'patch-1' of https://github.com/jplaverdure/sqlalchemy into tMike Bayer2014-02-161-3/+5
|\
| * Switched to UTC Timestamppr/41jplaverdure2013-11-081-2/+2
| |
| * Added changed(timestamp) on _history table and supprot for schemasjplaverdure2013-11-081-3/+5
| |
* | - Added a tweak to the "history_meta" example where the check forMike Bayer2014-02-021-1/+2
| | | | | | | | | | "history" on a relationship-bound attribute will now no longer emit any SQL if the relationship is unloaded.
* | specify run as module hereMike Bayer2013-12-071-5/+6
| |
* | - remove verbiage about "namespaces" from the dogpile example, [ticket:2862]Mike Bayer2013-12-073-12/+15
| | | | | | | | - fix broken py2k/py3k isms
* | - add a new example section for "join conditions", start puttingMike Bayer2013-12-053-0/+210
| | | | | | | | the primaryjoin examples there
* | - the pronoun removal commit. there was only one instance of aMike Bayer2013-11-302-3/+3
| | | | | | | | | | | | | | | | standalone gendered pronoun with a gender-neutral subject, but also have replaced all occurences of "his/her", "his or her", etc. The docs have always strived to account for both genders in any non-specific singular pronoun, however recent controversy in the community suggests that a zero-gendered-pronoun policy is probably best going forward.
* | forgot to add this, oopsieMike Bayer2013-11-303-0/+396
| |
* | simplify thisMike Bayer2013-11-301-20/+2
| |
* | - start reworking examples to include more code from the wiki.Mike Bayer2013-11-295-253/+156
| | | | | | | | | | - add the other versioning examples from the wiki - modernize the dictlike examples
* | - add a new sphinx extension "viewsource". takes advantage of part of the ↵Mike Bayer2013-11-0933-125/+108
| | | | | | | | | | | | | | | | | | viewcode extension to allow ad-hoc display of the source of any file, as well as a "directory listing" structure. - reorganize examples/ to take advantage of new extension. in particular, keep moving all the descriptive text for files etc. into module docstrings, taking more advantage of self-documentation.
* | - add proof of concept for versioning, [ticket:2861]Mike Bayer2013-11-081-1/+31
|/
* - Fixed bug which prevented history_meta recipe from working withMike Bayer2013-11-073-99/+81
| | | | | | joined inheritance schemes more than one level deep. - don't need to use _lib.py here anymore now that these features are in sqlalchemy.testing
* - reorganize docs so expression, schema are broken out into subfiles, ↵Mike Bayer2013-08-181-0/+1
| | | | | | they're too big - fix the targeting of module names moved around by using custom handlers for "Bases", etc.
* - changelogMike Bayer2013-08-171-26/+26
| | | | - clean up these tests to not use globals so much, close out the session
* Made primary_key autoincrement=False in versioning example.Patrick R. Schmid2013-07-311-3/+3
|
* modernize this a bitMike Bayer2013-07-271-19/+10
|
* - Improved the examples in ``examples/generic_associations``, includingMike Bayer2013-07-195-48/+194
| | | | | | | | | | | | | | | that ``discriminator_on_association.py`` makes use of single table inheritance do the work with the "discriminator". Also added a true "generic foreign key" example, which works similarly to other popular frameworks in that it uses an open-ended integer to point to any other table, foregoing traditional referential integrity. While we don't recommend this pattern, information wants to be free. Also in 0.8.3. - Added a convenience class decorator :func:`.as_declarative`, is a wrapper for :func:`.declarative_base` which allows an existing base class to be applied using a nifty class-decorated approach. Also in 0.8.3.
* Forgot final check that a delete in a backref also doesn't create a new versionMatt Chisholm2013-06-171-0/+3
| | | | follow up to https://bitbucket.org/zzzeek/sqlalchemy/pull-request/2
* don't create a history entry when an object in a backref has changedMatt Chisholm2013-06-152-3/+42
| | | | The code that determines whether an object in a relation has been added/removed does not take into account that that relation may be a backref. If the relation is a backref, then nothing on the current table is changing, and therefore no history entry should be created.
* Merge branch 'master' into rel_0_9Mike Bayer2013-05-281-1/+1
|\
| * Fixed a small bug in the dogpile example where the generationMike Bayer2013-05-281-1/+1
| | | | | | | | | | of SQL cache keys wasn't applying deduping labels to the statement the same way :class:`.Query` normally does.
* | - the raw 2to3 runMike Bayer2013-04-2729-296/+296
|/ | | | - went through examples/ and cleaned out excess list() calls
View Lorry Controller Status