Commits

Author Commit Message Labels Comments Date
Mike Bayer
- Fixed bug in SQLite dialect where reflection of UNIQUE constraints that included non-alphabetic characters in the names, like dots or spaces, would not be reflected with their name. fixes #3495 (cherry picked from commit f39e692d1249aeffb4de85987f6a74303fc5dcc5) Conflicts: lib/sqlalchemy/dialects/sqlite/base.py
Branches
rel_0_9
Mike Bayer
- Fixed bug in SQLite dialect where reflection of UNIQUE constraints that included non-alphabetic characters in the names, like dots or spaces, would not be reflected with their name. fixes #3495
Mike Bayer
- Fixed an issue where a particular base class within utils 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
Mike Bayer
1.0.7
Tags
rel_1_0_7
Mike Bayer
- changelog for #3459, fixes #3459 - test for .cast() method has no good place now except for test_cast in test_compiler.py
Mike Bayer
Merge branch 'bb_issue_3459' of https://bitbucket.org/xflr6/sqlalchemy into pr56
Mike Bayer
- Fixed regression where new methods on :class:`.ResultProxy` used 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
Mike Bayer
- pg8000 very annoyingly complaining here, use total literal
Mike Bayer
- Fixed regression where :meth:`.ResultProxy.keys` would return 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
Mike Bayer
- Fixed bug where coersion of literal ``True`` or ``False`` constant in conjunction with :func:`.and_` or :func:`.or_` would fail with an AttributeError. fixes #3490
Mike Bayer
- Fixed potential issue where a custom subclass 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
Jakub Stasiak
Remove RootTransaction<->RootTransaction reference cycle (cherry picked from commit 3ef00e816da042d4932be53b86f76db17c800842)
Mike Bayer
- db_opts doesn't need to be a global since we no longer have any global option for it. keep it local to production of config so values don't leak in a multi --db situation.
Mike Bayer
- fix these two tests
Mike Bayer
- changelog for pr github:188
Mike Bayer
Merge remote-tracking branch 'origin/pr/188' into pr188
Mike Bayer
- version specs for new Sequence arguments - changelog for pullreq github:186
Mike Bayer
Merge remote-tracking branch 'origin/pr/186' into pr186
dan-gittik
Added test for modulo operator.
dan-gittik
Added support for reflected modulo operator.
Mike Bayer
- add a note, references #3487
Mike Bayer
- Fixed bug in :class:`.AbstractConcreteBase` extension where 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
Mike Bayer
- try to note under insert.values(), if you need "multiple parameter sets" there is a much more common case which works equally well for INSERT/UPDATE/DELETE e.g. executemany(). reference #3476
Branches
rel_0_9
Mike Bayer
- try to note under insert.values(), if you need "multiple parameter sets" there is a much more common case which works equally well for INSERT/UPDATE/DELETE e.g. executemany(). reference #3476
Mike Bayer
- add a warning suggesting to use the dictionary form of access if the name of the attribute being accessed is non-specific, thereby avoiding collisions on names like items, values, keys. fixes #3475 (cherry picked from commit 6fcc5d4a07e5c409a7d8438582598d0e90562ea0)
Branches
rel_0_9
Mike Bayer
- add a warning suggesting to use the dictionary form of access if the name of the attribute being accessed is non-specific, thereby avoiding collisions on names like items, values, keys. fixes #3475
Mike Bayer
- fix the link here fixes 3473 (cherry picked from commit cf21497f02e64b6ddec82e12a7c26b9476616b00)
Branches
rel_0_9
Mike Bayer
- fix the link here fixes 3473
Mike Bayer
- increase the varchar here
Mike Bayer
- Fixed 1.0 regression where value objects that override ``__eq__()`` to return a non-boolean-capable object, such as some geoalchemy types as well as numpy types, were being tested for ``bool()`` during a unit of work update operation, where in 0.9 the return value of ``__eq__()`` was tested against "is True" to guard against this. fixes #3469
  1. Prev
  2. Next