summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* re.match to re.searchpr/26Scott Schaefer2013-09-061-1/+1
| | | | | Convert to re.search to eliminate the restriction on only matching the beginning of the string
* Fixed Query.exists() method for the case, when query doesn't have any ↵Vladimir Magamedov2013-09-044-2/+26
| | | | filters applied.
* add caveats regarding RETURNINGMike Bayer2013-09-022-3/+59
|
* use a different col here to keep oracle happyMike Bayer2013-09-021-2/+12
|
* plus some more adjustments for mysql, or in general if an Index refers toMike Bayer2013-08-282-2/+12
| | | | in-python only cols
* Fixed bug where using the ``column_reflect`` event to change the ``.key``Mike Bayer2013-08-284-10/+68
| | | | | | of the incoming :class:`.Column` would prevent primary key constraints, indexes, and foreign key constraints from being correctly reflected. Also in 0.8.3. [ticket:2811]
* - fix bug here in profiling.pyMike Bayer2013-08-282-12/+12
| | | | - callcount
* repair missing oracle skipMike Bayer2013-08-281-1/+1
|
* comment this alternative approach...Mike Bayer2013-08-281-0/+7
|
* - these tests now fail on a normalize name DB, as they should! because we're ↵Mike Bayer2013-08-281-0/+6
| | | | quoting the lowercase name.
* - rework the profile thing to just rewrite all failing numbers when ↵Mike Bayer2013-08-282-8/+20
| | | | | | --write-profiles is set - some sqlite callcounts
* callcountsMike Bayer2013-08-272-3/+3
|
* - cx_oracle seems to have a bug here though it is hard to track downMike Bayer2013-08-274-14/+15
| | | | - cx_oracle dialect doesn't use normal col names, lets just not rely on that for now
* more seealsos...Mike Bayer2013-08-271-3/+4
|
* - A rework to the way that "quoted" identifiers are handled, in thatMike Bayer2013-08-2723-192/+622
| | | | | | | | | | | | | | | | instead of relying upon various ``quote=True`` flags being passed around, these flags are converted into rich string objects with quoting information included at the point at which they are passed to common schema constructs like :class:`.Table`, :class:`.Column`, etc. This solves the issue of various methods that don't correctly honor the "quote" flag such as :meth:`.Engine.has_table` and related methods. The :class:`.quoted_name` object is a string subclass that can also be used explicitly if needed; the object will hold onto the quoting preferences passed and will also bypass the "name normalization" performed by dialects that standardize on uppercase symbols, such as Oracle, Firebird and DB2. The upshot is that the "uppercase" backends can now work with force-quoted names, such as lowercase-quoted names and new reserved words. [ticket:2812]
* correct for missing fail() methods which were lost when we removed ↵Mike Bayer2013-08-261-25/+20
| | | | unittest.TestCase
* clean up formatting and other linting issuesMike Bayer2013-08-261-52/+51
|
* - ensure rowcount is returned for an UPDATE with no implicit returningMike Bayer2013-08-255-36/+35
| | | | | - modernize test for that - use py3k compatible next() in test_returning/test_versioning
* - fix server-side non-returning exampleMike Bayer2013-08-251-3/+4
| | | | - mention eager_defaults
* migration for version id feature, eager_defaultsMike Bayer2013-08-251-0/+44
|
* - restore constructor docs blown away in the mergeMike Bayer2013-08-251-0/+141
|
* - The ``version_id_generator`` parameter of ``Mapper`` can now be specifiedMike Bayer2013-08-2518-235/+896
| | | | | | | | | | | | | | | | | | | | | to rely upon server generated version identifiers, using triggers or other database-provided versioning features, by passing the value ``False``. The ORM will use RETURNING when available to immediately load the new version identifier, else it will emit a second SELECT. [ticket:2793] - The ``eager_defaults`` flag of :class:`.Mapper` will now allow the newly generated default values to be fetched using an inline RETURNING clause, rather than a second SELECT statement, for backends that support RETURNING. - Added a new variant to :meth:`.ValuesBase.returning` called :meth:`.ValuesBase.return_defaults`; this allows arbitrary columns to be added to the RETURNING clause of the statement without interfering with the compilers usual "implicit returning" feature, which is used to efficiently fetch newly generated primary key values. For supporting backends, a dictionary of all fetched values is present at :attr:`.ResultProxy.returned_defaults`. - add a glossary entry for RETURNING - add documentation for version id generation, [ticket:867]
* forgot to add system to the copy() methodMike Bayer2013-08-252-0/+8
| | | | | Conflicts: lib/sqlalchemy/schema.py
* added "system=True" to Column, so that we generally don't have to botherMike Bayer2013-08-256-7/+47
| | | | with CreateColumn rules
* Merge pull request #23 from yoloseem/mastermike bayer2013-08-252-3/+3
|\ | | | | Fixed two typos.
| * fix typospr/23Hyunjun Kim2013-08-252-3/+3
| |
* | - The :class:`.CreateColumn` construct can be appled to a customMike Bayer2013-08-245-4/+65
|/ | | | | compilation rule which allows skipping of columns, by producing a rule that returns ``None``. Also in 0.8.3.
* - "primary mapper entity" is now an attribute on Query,Mike Bayer2013-08-241-16/+11
| | | | | | | | making _MapperEntity slightly less dependent on a particular parent Query (in theory more shareable by multiple Query objects in different contexts) - remove some comments that have been misunderstanding what _mapper_entities does, or perhaps forgot to get removed - simplify _mapper_entities
* formattingMike Bayer2013-08-231-5/+5
|
* - update the test times, include pypy, clean up the scriptMike Bayer2013-08-211-19/+29
|
* add FAQ entry on large insertsMike Bayer2013-08-211-1/+127
|
* fix linkMike Bayer2013-08-211-1/+1
|
* move FAQ to the docs, [ticket:2133]Mike Bayer2013-08-2111-7/+791
|
* yikes return the modname if no lookup found...Mike Bayer2013-08-211-0/+2
|
* Fixed bug where list instrumentation would fail to represent aMike Bayer2013-08-205-4/+42
| | | | | | | | setslice of ``[0:0]`` correctly, which in particular could occur when using ``insert(0, item)`` with the association proxy. Due to some quirk in Python collections, the issue was much more likely with Python 3 rather than 2. Also in 0.8.3, 0.7.11. [ticket:2807]
* too small!Mike Bayer2013-08-181-1/+1
|
* add some heightMike Bayer2013-08-181-2/+5
|
* additoinalMike Bayer2013-08-182-18/+45
|
* - reorganize docs so expression, schema are broken out into subfiles, ↵Mike Bayer2013-08-1831-1890/+1936
| | | | | | they're too big - fix the targeting of module names moved around by using custom handlers for "Bases", etc.
* and we don't need weaksetMike Bayer2013-08-182-24/+1
|
* 0.9 needs 0.8's changelog also.....Mike Bayer2013-08-181-0/+10
|
* - use newly fixed WeakSequence (#2794) to not have to rely on class name for ↵Mike Bayer2013-08-181-5/+4
| | | | sorting in #2779
* - add WeakSequence.append()Mike Bayer2013-08-182-6/+43
| | | | - fix and test weakref cleanout for WeakSequence, [ticket:2794]
* formattingMike Bayer2013-08-181-1/+2
|
* Fixed a potential issue in an ordered sequence implementation usedMike Bayer2013-08-184-5/+29
| | | | | | | by the ORM to iterate mapper hierarchies; under the Jython interpreter this implementation wasn't ordered, even though cPython and Pypy maintained ordering. Also in 0.8.3. [ticket:2794]
* - also do delete, add seealsos, formatting, etc. [ticket:2798]Mike Bayer2013-08-181-13/+37
|
* - add better notes to query.update(), most notably how to deal with a joined ↵Mike Bayer2013-08-182-12/+38
| | | | | | table update, [ticket:2798]
* Fixed regression dating back to 0.7.9 whereby the name of a CTE mightMike Bayer2013-08-185-1/+40
| | | | | not be properly quoted if it was referred to in multiple FROM clauses. Also in 0.8.3, 0.7.11. [ticket:2801]
* more tests regarding expiry, deferralMike Bayer2013-08-171-1/+57
|
* some tests regarding how newly inserted rows are treated as far as fetch on ↵Mike Bayer2013-08-171-1/+91
| | | | access
View Lorry Controller Status