MCPcopy
hub / github.com/sqlalchemy/sqlalchemy / order_by_col_from_union

Method order_by_col_from_union

test/requirements.py:882–903  ·  view source on GitHub ↗

target database supports ordering by a column from a SELECT inside of a UNION E.g. (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id Fails on SQL Server and oracle. Previously on Oracle, prior to #8221, the ROW_NUMBER subquerying applied to queries allow

(self)

Source from the content-addressed store, hash-verified

880
881 @property
882 def order_by_col_from_union(self):
883 """target database supports ordering by a column from a SELECT
884 inside of a UNION
885
886 E.g. (SELECT id, ...) UNION (SELECT id, ...) ORDER BY id
887
888 Fails on SQL Server and oracle.
889
890 Previously on Oracle, prior to #8221, the ROW_NUMBER subquerying
891 applied to queries allowed the test at
892 suite/test_select.py ->
893 CompoundSelectTest.test_limit_offset_selectable_in_unions
894 to pass, because of the implicit subquerying thus creating a query
895 that was more in line with the syntax
896 illustrated at
897 https://stackoverflow.com/a/6036814/34549. However, Oracle doesn't
898 support the above (SELECT ..) UNION (SELECT ..) ORDER BY syntax
899 at all. So those tests are now not supported w/ Oracle as of
900 #8221.
901
902 """
903 return fails_if(["mssql", "oracle < 23"])
904
905 @property
906 def parens_in_union_contained_select_w_limit_offset(self):

Callers

nothing calls this directly

Calls 1

fails_ifFunction · 0.90

Tested by

no test coverage detected