summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Support get_schema_names for SQLitepr/198Brian Van Klaveren2015-09-091-0/+5
| | | Should return "main" and the names of attached databases.
* Support get_schema_names for SQLiteBrian Van Klaveren2015-09-091-0/+7
|
* - Fixed two issues regarding Sybase reflection, allowing tablesMike Bayer2015-08-102-6/+20
| | | | | | | | | without primary keys to be reflected as well as ensured that a SQL statement involved in foreign key detection is pre-fetched up front to avoid driver issues upon nested queries. Fixes here courtesy Eugene Zapolsky; note that we cannot currently test Sybase to locally verify these changes. fixes #3508 fixes #3509
* Merge pull request #192 from halfcrazy/patch-1mike bayer2015-08-091-1/+1
|\ | | | | fix typo int->into
| * fix typo int->intopr/192halfcrazy2015-08-091-1/+1
|/
* Merge pull request #191 from leorochael/leorochael-remove_dead_variablemike bayer2015-08-061-3/+0
|\ | | | | Remove useless code
| * Remove useless codepr/191Leonardo Rochael Almeida2015-08-061-3/+0
|/ | | `to_unicode` variable was created but was not used.
* - add a note clarifying query.with_labels(), fixes #3506Mike Bayer2015-08-031-0/+10
|
* - Fixed issue where the SQL Server dialect would reflect a string-Mike Bayer2015-07-304-5/+83
| | | | | | | | | | | | or other variable-length column type with unbounded length by assigning the token ``"max"`` to the length attribute of the string. While using the ``"max"`` token explicitly is supported by the SQL Server dialect, it isn't part of the normal contract of the base string types, and instead the length should just be left as None. The dialect now assigns the length to None on reflection of the type so that the type behaves normally in other contexts. fixes #3504
* - Fixed support for cx_Oracle version 5.2, which was trippingMike Bayer2015-07-292-2/+16
| | | | | | | | up SQLAlchemy's version detection under Python 3 and inadvertently not using the correct unicode mode for Python 3. This would cause issues such as bound variables mis-interpreted as NULL and rows silently not being returned. fixes #3491
* - fix typo in suffix_with() docs, fixes #3502Mike Bayer2015-07-291-1/+1
|
* - work to bridge between core/ORM tutorials regarding the text() constructMike Bayer2015-07-262-8/+31
|
* - remove "completely raw", whatever that isMike Bayer2015-07-261-21/+16
|
* - typoMike Bayer2015-07-261-1/+1
|
* - add an example of text.columnsMike Bayer2015-07-261-4/+19
| | | | - correct the scalar() example output
* - remove "distutils-only" mode, use setuptools onlyMike Bayer2015-07-244-109/+109
| | | | | | - add first-class "pytest" runner to setup.py, fixes #3489 - remove references to setuptools Feature and mark that "--without-cextensions" is removed, fixes #3500
* - Organize the tree for 1.1Mike Bayer2015-07-249-15/+107
|
* - An adjustment to the new Postgresql feature of reflecting storageMike Bayer2015-07-244-2/+20
| | | | | | | | | options and USING of :ticket:`3455` released in 1.0.6, to disable the feature for Postgresql versions < 8.2 where the ``reloptions`` column is not provided; this allows Amazon Redshift to again work as it is based on an 8.0.x version of Postgresql. Fix courtesy Pete Hollobon. references #3455
* 1.0.8rel_1_0_8Mike Bayer2015-07-222-2/+3
|
* - categorize this correctlyMike Bayer2015-07-221-1/+1
|
* - Fixed critical issue whereby the pool "checkout" event handlerMike Bayer2015-07-223-1/+117
| | | | | | | | | | | | may be called against a stale connection without the "connect" event handler having been called, in the case where the pool attempted to reconnect after being invalidated and failed; the stale connection would remain present and would be used on a subsequent attempt. This issue has a greater impact in the 1.0 series subsequent to 1.0.2, as it also delivers a blanked-out ``.info`` dictionary to the event handler; prior to 1.0.2 the ``.info`` dictionary is still the previous one. fixes #3497
* 0.9.10 release dateMike Bayer2015-07-221-0/+1
| | | | (cherry picked from commit e71cf56a835842cd7d7038d6527888cc1297005f)
* - Fixed bug in SQLite dialect where reflection of UNIQUE constraintsMike Bayer2015-07-213-1/+18
| | | | | | that included non-alphabetic characters in the names, like dots or spaces, would not be reflected with their name. fixes #3495
* - Fixed an issue where a particular base class within utilsMike Bayer2015-07-207-11/+57
| | | | | | | | | didn't implement ``__slots__``, and therefore meant all subclasses of that class didn't either, negating the rationale for ``__slots__`` to be in use. Didn't cause any issue except on IronPython which apparently does not implement ``__slots__`` behavior compatibly with cPython. Fixes #3494
* 1.0.7rel_1_0_7Mike Bayer2015-07-202-2/+3
|
* - changelog for #3459, fixes #3459Mike Bayer2015-07-194-8/+15
| | | | | - test for .cast() method has no good place now except for test_cast in test_compiler.py
* Merge branch 'bb_issue_3459' of https://bitbucket.org/xflr6/sqlalchemy into pr56Mike Bayer2015-07-192-0/+14
|\
| * add ClauseElement.cast() shortcut-methodSebastian Bank2015-06-192-0/+14
| |
* | - Fixed regression where new methods on :class:`.ResultProxy` usedMike Bayer2015-07-193-4/+33
| | | | | | | | | | | | | | | | | | by the ORM :class:`.Query` object (part of the performance enhancements of :ticket:`3175`) would not raise the "this result does not return rows" exception in the case where the driver (typically MySQL) fails to generate cursor.description correctly; an AttributeError against NoneType would be raised instead. fixes #3481
* | - pg8000 very annoyingly complaining here, use total literalMike Bayer2015-07-191-1/+2
| |
* | - Fixed regression where :meth:`.ResultProxy.keys` would returnMike Bayer2015-07-196-12/+123
| | | | | | | | | | | | | | | | un-adjusted internal symbol names for "anonymous" labels, which are the "foo_1" types of labels we see generated for SQL functions without labels and similar. This was a side effect of the performance enhancements implemented as part of references #918. fixes #3483
* | - Fixed bug where coersion of literal ``True`` or ``False`` constantMike Bayer2015-07-193-2/+71
| | | | | | | | | | | | in conjunction with :func:`.and_` or :func:`.or_` would fail with an AttributeError. fixes #3490
* | - Fixed potential issue where a custom subclassMike Bayer2015-07-193-3/+31
| | | | | | | | | | | | | | of :class:`.FunctionElement` or other column element that incorrectly states 'None' or any other invalid object as the ``.type`` attribute will report this exception instead of recursion overflow. fixes #3485
* | Remove RootTransaction<->RootTransaction reference cycleJakub Stasiak2015-07-181-1/+5
| | | | | | | | (cherry picked from commit 3ef00e816da042d4932be53b86f76db17c800842)
* | - db_opts doesn't need to be a global since we no longer have any globalMike Bayer2015-07-172-6/+4
| | | | | | | | | | option for it. keep it local to production of config so values don't leak in a multi --db situation.
* | - fix these two testsMike Bayer2015-07-171-2/+2
| |
* | - changelog for pr github:188Mike Bayer2015-07-171-0/+8
| |
* | Merge remote-tracking branch 'origin/pr/188' into pr188Mike Bayer2015-07-172-0/+11
|\ \
| * | Added test for modulo operator.pr/188Dan Gittik2015-07-171-0/+3
| | |
| * | Added support for reflected modulo operator.Dan Gittik2015-07-171-0/+8
| | |
* | | - version specs for new Sequence argumentsMike Bayer2015-07-172-0/+23
| | | | | | | | | | | | - changelog for pullreq github:186
* | | Merge remote-tracking branch 'origin/pr/186' into pr186Mike Bayer2015-07-174-4/+84
|\ \ \ | |/ / |/| |
| * | add CYCLE support to Sequence() and docstrings for NO MINVALUE and NO MAXVALUEpr/186jakeogh2015-06-274-5/+39
| | |
| * | add NO MINVALUE and NO MAXVALUE support to Sequence()jakeogh2015-06-274-3/+20
| | |
| * | add MAXVALUE support to Sequence()jakeogh2015-06-274-5/+21
| | |
| * | add MINVALUE support to Sequence()jakeogh2015-06-274-4/+17
| | |
* | | - add a note, references #3487Mike Bayer2015-07-151-0/+10
| | |
* | | - Fixed bug in :class:`.AbstractConcreteBase` extension whereMike Bayer2015-07-134-2/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | a column setup on the ABC base which had a different attribute name vs. column name would not be correctly mapped on the final base class. The failure on 0.9 would be silent whereas on 1.0 it raised an ArgumentError, so may not have been noticed prior to 1.0. fixes #3480
* | | - try to note under insert.values(), if you needMike Bayer2015-07-082-4/+12
| | | | | | | | | | | | | | | | | | "multiple parameter sets" there is a much more common case which works equally well for INSERT/UPDATE/DELETE e.g. executemany(). reference #3476
* | | - add a warning suggesting to use the dictionary form of accessMike Bayer2015-07-051-0/+33
| | | | | | | | | | | | | | | | | | if the name of the attribute being accessed is non-specific, thereby avoiding collisions on names like items, values, keys. fixes #3475