summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* - properly handle negative indexes in RowProxy.__getitem__()pr/231Lele Gaifax2016-01-283-1/+31
|
* - experimental - try out a very open ended design for the factors, assumeMike Bayer2016-01-271-26/+15
| | | | | many more combinations of factors are possible and basically make them more akin to command options at the tox level.
* - reinstate "dont set up integer index in keymap if we're on cexts",Mike Bayer2016-01-272-6/+11
| | | | | and this time also fix the cext itself to properly handle int vs. long on py2k
* - restore the use of PYTHONNOUSERSITE that was removedMike Bayer2016-01-272-6/+39
| | | | | | | | | | in df3f125bd84fc7ec5d45592c5774daf3a39d9bc9, this flag is explicitly checked within conftest.py and we need to continue to use it, otherwise a tox build inside of .tox that isn't usedevelop is ignored, including C extensions - rework the whole system of running with coverage, so that with coverage, we *are* using usedevelop, but also make sure we rm the .so files for nocext, make sure we --cov-append, etc.
* Revert "- dont set up integer index in keymap if we're on cexts"Mike Bayer2016-01-271-10/+5
| | | | | | This reverts commit de0d144a395c31eb74084177df95a4858b830f88. Apparently the test suite is not using the cextensions correctly at the moment.
* - dont set up integer index in keymap if we're on cextsMike Bayer2016-01-271-5/+10
|
* fix %x string format to compatible with Python 3.5Ruilin Huang2016-01-271-1/+1
|
* fix %x string format to compatible with Python 3.5xghrl2016-01-271-1/+1
|
* - unfortunately we need to match within join where col.key does not matchMike Bayer2016-01-261-2/+1
| | | | | what's given so we need to use a set() here. contains_column is not within any performance paths
* - rework ColumnCollection to no longer persist "all_col_set"; we don'tMike Bayer2016-01-263-20/+39
| | | | | | | | | | | | | need this collection except in the extend/update uses where we create it ad-hoc. simplifies pickling. Compatibility with 1.0 should be OK as ColumnColleciton uses __getstate__ in any case and the __setstate__ contract hasn't changed. - Fixed bug in :class:`.Table` metadata construct which appeared around the 0.9 series where adding columns to a :class:`.Table` that was unpickled would fail to correctly establish the :class:`.Column` within the 'c' collection, leading to issues in areas such as ORM configuration. This could impact use cases such as ``extend_existing`` and others. fixes #3632
* - The workaround for right-nested joins on SQLite, where they are rewrittenMike Bayer2016-01-266-104/+235
| | | | | | | | | | as subqueries in order to work around SQLite's lack of support for this syntax, is lifted when SQLite version 3.7.16 or greater is detected. fixes #3634 - The workaround for SQLite's unexpected delivery of column names as ``tablename.columnname`` for some kinds of queries is now disabled when SQLite version 3.10.0 or greater is detected. fixes #3633
* remove PYTHONNOUSERSITE, not sure why this was here, it apparently ↵Mike Bayer2016-01-261-3/+0
| | | | interferes with coverage
* - another approach at coverageMike Bayer2016-01-261-32/+26
|
* - try to improve the default coverage jobMike Bayer2016-01-261-1/+2
|
* - fix the deps for the last changeMike Bayer2016-01-241-6/+6
|
* - unfortunately we have to force the paths to be shorter due toMike Bayer2016-01-241-7/+7
| | | | https://github.com/pypa/virtualenv/issues/596
* - add a new qualifier "native" vs. "dbapi" unicode to avoidMike Bayer2016-01-247-494/+450
| | | | | | profiling problems here - add extras_require to setup.py for the most common DBAPIs - rework tox.ini to use extras, specify a test matrix built in
* - fix array test that was essentially taking a weird guessMike Bayer2016-01-231-2/+2
| | | | | | at the primary key of a row based on other tests invoking around it (cherry picked from commit 7d70dfd412c05fd8349339da01b472bd3df02082)
* - fix stray connectionMike Bayer2016-01-231-1/+4
|
* - restate the "secondary" / AssociationProxy warning more strongly.Mike Bayer2016-01-231-10/+52
| | | | references #3638
* - use regex here, columns dont matter, keep coming up with different orderingsMike Bayer2016-01-231-3/+3
|
* - use uuid fragments for provision names to enable multiple test suitesMike Bayer2016-01-231-2/+2
| | | | per server
* - native unicode expectations are too difficult to maintainMike Bayer2016-01-231-60/+0
| | | | w/ the number of drivers /DBURIs / python versions
* - move out match compiler test to test_compilerMike Bayer2016-01-232-23/+11
| | | | - test_query isn't assertscompiledsql
* - make this test deterministicMike Bayer2016-01-211-3/+3
|
* - add a forwards-test here as wellMike Bayer2016-01-211-0/+4
|
* - documenation updates to clarify specific SQLite versionsMike Bayer2016-01-213-13/+41
| | | | | | | | | that have problems with right-nested joins and UNION column keys; references #3633 references #3634. backport from 1.1 to 0.9 announcing 1.1 as where these behaviors will be retired based on version-specific checks - fix test_resultset so that it passes when SQLite 3.10.0 is present, references #3633
* - Added new parameter :paramref:`.orm.mapper.passive_deletes` toMike Bayer2016-01-207-2/+367
| | | | | | | | available mapper options. This allows a DELETE to proceed for a joined-table inheritance mapping against the base table only, while allowing for ON DELETE CASCADE to handle deleting the row from the subclass tables. fixes #2349
* - The unsupported Sybase dialect now raises ``NotImplementedError``Mike Bayer2016-01-203-8/+20
| | | | | when attempting to compile a query that includes "offset"; Sybase has no straightforward "offset" feature. fixes #2278
* - generalize the verbiage on LargeBinary so that it doesn'tMike Bayer2016-01-202-12/+5
| | | | create confusion for inherited classes such as BYTEA, fixes
* - update oracle JDBC driver URL, fixes #3554Mike Bayer2016-01-201-2/+1
|
* - cross link for concrete helper classesMike Bayer2016-01-203-71/+36
| | | | | - remove redundant concrete helper docs from declarative docs, two places is enough
* - typoMike Bayer2016-01-201-1/+1
| | | | (cherry picked from commit b53667526eb9b2fabccfb097a5b76906d6452249)
* - redo the docs for concrete inheritance to more stronglyMike Bayer2016-01-202-50/+241
| | | | favor declarative, fixes #2890
* - clarify the "Adding" section also illustrates updates, fixes #2942Mike Bayer2016-01-201-3/+6
|
* - add a note that the literal_binds flag should be usedMike Bayer2016-01-201-1/+11
| | | | when cross-compiling from DDL to SQL, fixes #3615
* Fix ArrayOfEnum's handling of empty arrays.pr/229Chase2016-01-191-1/+1
| | | Prior to this change a value of `'{}'` would split into the list `['']`.
* - the order in which _generate_backref() for different mappers is calledMike Bayer2016-01-191-1/+1
| | | | | is random; therefore it may be called against the subclass mapper first, so need to check .concrete on both sides, references #3630
* - calling str() on a core sql construct has been made more "friendly",Mike Bayer2016-01-1911-11/+180
| | | | | | | | | | when the construct contains non-standard sql elements such as returning, array index operations, or dialect-specific or custom datatypes. a string is now returned in these cases rendering an approximation of the construct (typically the postgresql-style version of it) rather than raising an error. fixes #3631 - add within_group to top-level imports - add eq_ignore_whitespace to sqlalchemy.testing imports
* - Fixed issue where two same-named relationships that refer toMike Bayer2016-01-195-10/+128
| | | | | | | | a base class and a concrete-inherited subclass would raise an error if those relationships were set up using "backref", while setting up the identical configuration using relationship() instead with the conflicting names would succeed, as is allowed in the case of a concrete mapping. fixes #3630
* - The ``str()`` call for :class:`.Query` will now take into accountMike Bayer2016-01-195-10/+135
| | | | | | | | | | | | the :class:`.Engine` to which the :class:`.Session` is bound, when generating the string form of the SQL, so that the actual SQL that would be emitted to the database is shown, if possible. Previously, only the engine associated with the :class:`.MetaData` to which the mappings are associated would be used, if present. If no bind can be located either on the :class:`.Session` or on the :class:`.MetaData` to which the mappings are associated, then the "default" dialect is used to render the SQL, as was the case previously. fixes #3081
* - Fixed bug where some exception re-raise scenarios would attachMike Bayer2016-01-183-12/+79
| | | | | | | | the exception to itself as the "cause"; while the Python 3 interpreter is OK with this, it could cause endless loops in iPython. fixes #3625 - add tests for reraise, raise_from_cause - raise_from_cause is the same on py2k/3k, use just one function
* Merge remote-tracking branch 'origin/pr/227'Mike Bayer2016-01-161-2/+2
|\
| * Fix typo in relationships docspr/227rmn2016-01-161-2/+2
| |
* | - fix People -> Person , fixes #3628Mike Bayer2016-01-161-1/+1
|/
* - updateMike Bayer2016-01-141-1/+1
|
* - illustrate these using the newer exception doctest format.Mike Bayer2016-01-141-26/+8
| | | | | unfortunately we can't show the SQL unless we filtered it out from doctest...not worth it
* - A deep improvement to the recently added :meth:`.TextClause.columns`Mike Bayer2016-01-1415-599/+1237
| | | | | | | | | | | | | | | | | | | method, and its interaction with result-row processing, now allows the columns passed to the method to be positionally matched with the result columns in the statement, rather than matching on name alone. The advantage to this includes that when linking a textual SQL statement to an ORM or Core table model, no system of labeling or de-duping of common column names needs to occur, which also means there's no need to worry about how label names match to ORM columns and so-forth. In addition, the :class:`.ResultProxy` has been further enhanced to map column and string keys to a row with greater precision in some cases. fixes #3501 - reorganize the initialization of ResultMetaData for readability and complexity; use the name "cursor_description", define the task of "merging" cursor_description with compiled column information as its own function, and also define "name extraction" as a separate task. - fully change the name we use in the "ambiguous column" error to be the actual name that was ambiguous, modify the C ext also
* - there was a DATEPART test after all, fix formatMike Bayer2016-01-141-1/+1
|
* - fix some old verbiage that refers to text() as an "implicit" thingMike Bayer2016-01-141-8/+7
| | | | | for SQL fragments; we've deprecated that in 1.0 and its a good idea to document like this for 0.9 as well.
View Lorry Controller Status