kallithea Changeset - 3ed43530d3b8

Changeset - 3ed43530d3b8

Parent rev.

Child rev.

[Not reviewed]

default

0 1 0

Søren Løvborg - 9 years ago 2017-03-27 11:29:38
sorenl@unity3d.com

db: upgrade to SQLAlchemy 1.1, fixing invalid PostgreSQL SQL in User.is_default_user

eea19c23b741 triggered a bug in SQLAlchemy 1.0.17, causing invalid SQL to be
emitted for PostgreSQL: For the (Python) query '(x == y) == z', SQLAlchemy
generates the SQL 'x = y = z'. SQLite and MySQL accepts this, but PostgreSQL
does not. This bug has been fixed in 1.1.

Testing and review shows no problems with 1.1

1 file changed with 1 insertions and 1 deletions:

setup.py

0 comments (0 inline, 0 general)

setup.py

➞

Show inline comments

@@ @@ -36,25 +36,25 @@ is_windows = __platform__ in ['Windows'] @@
 requirements = [
     "alembic>=0.8.0,<0.9",
     "GearBox<1",
     "waitress>=0.8.8,<1.0",
     "webob>=1.7,<2",
     "backlash >= 0.1.2, < 1.0.0",
     "TurboGears2 >= 2.3.10, < 3.0.0",
     "tgext.routes >= 0.2.0, < 1.0.0",
     "Beaker>=1.7.0,<2",
     "WebHelpers==1.3",
     "formencode>=1.2.4,<=1.2.6",
-    "SQLAlchemy>=1.0,<1.1",
+    "SQLAlchemy>=1.1,<1.2",
     "Mako>=0.9.0,<=1.0.0",
     "pygments>=1.5",
     "whoosh>=2.5.0,<=2.5.7",
     "celery>=3.1,<3.2",
     "babel>=0.9.6,<2.4",
     "python-dateutil>=1.5.0,<2.0.0",
     "markdown==2.2.1",
     "docutils>=0.8.1",
     "URLObject==2.3.4",
     "Routes==1.13",
     "dulwich>=0.14.1",
     "mercurial>=2.9,<4.2",

0 comments (0 inline, 0 general)