File: alias_qualification_order_by.test

package info (click to toggle)
duckdb 1.5.1-2
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 299,196 kB
  • sloc: cpp: 865,414; ansic: 57,292; python: 18,871; sql: 12,663; lisp: 11,751; yacc: 7,412; lex: 1,682; sh: 747; makefile: 558
file content (44 lines) | stat: -rw-r--r-- 877 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# name: test/sql/binder/alias_qualification_order_by.test
# description: Test alias.name resolution in ORDER BY clause
# group: [binder]

# simple ordering by projection alias
query I
SELECT a AS x FROM (VALUES (3),(1),(2)) t(a)
ORDER BY alias.x;
----
1
2
3

# ordering by a later alias derived from a prior alias
query II
SELECT a + 1 AS x, alias.x * 10 AS y FROM (VALUES (1),(3),(2)) t(a)
ORDER BY alias.y DESC;
----
4	40
3	30
2	20

# quoted alias in ORDER BY
query I
SELECT a AS "MiXeD" FROM (VALUES (2),(1)) t(a)
ORDER BY alias."MiXeD";
----
1
2

# ensure a table actually named `alias` still works and does not conflict with alias references
statement ok
CREATE TABLE alias (v INT);

statement ok
INSERT INTO alias VALUES (20), (10);

# Table-qualified column should be prioritized when resolving alias.<name>
query I
SELECT v AS x FROM alias
ORDER BY alias.v;
----
10
20