]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e967c13) | patch
Consider default FROM DUAL for MySQL
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 28 Jul 2020 20:46:53 +0000 (16:46 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 29 Jul 2020 17:20:33 +0000 (13:20 -0400)
commite41998981c0d1d539091bfd8a30c1f7132237a3d
treeb786823a97763006d94d03895e733fa40a7cfbaetree | snapshot
parente967c13e0878f4d5f8fbdb6584261d0a92e7c1a3commit | diff
Consider default FROM DUAL for MySQL

MySQL claims it doesn't require FROM DUAL for no
FROM clause even though the issue at #5481 locates
a case which requires one.  See if FROM DUAL the same
way as Oracle without attempting to guess is potentially
feasible.

Fixes: #5481
Change-Id: I2a28876c10a8ce2d121cd344dcdd837db321d4ab
(cherry picked from commit 59b65b3008de5d6c5e4318846d04e50e5851e957)
doc/build/changelog/unreleased_13/5481.rst [new file with mode: 0644] blob
lib/sqlalchemy/dialects/mysql/base.py diff | blob | blame | history
lib/sqlalchemy/testing/suite/test_select.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git