提交 95a33fb4 编写于 作者: A Asim R P 提交者: Taylor Vesely

Use distinct schema in tests having table name collisions

Co-authored-by: NAsim R P <apraveen@pivotal.io>
Co-authored-by: NTaylor Vesely <tvesely@pivotal.io>
上级 a13a8981
......@@ -7369,7 +7369,7 @@ create view v1 as
select dt, sum(cn) over(order by grouping(cn) range grouping(cn) preceding)
from sale group by rollup(cn,dt);
\d+ v1
View "public.v1"
View "olap_window_seq.v1"
Column | Type | Modifiers | Storage | Description
--------+--------+-----------+---------+-------------
dt | date | | plain |
......
......@@ -7371,7 +7371,7 @@ create view v1 as
select dt, sum(cn) over(order by grouping(cn) range grouping(cn) preceding)
from sale group by rollup(cn,dt);
\d+ v1
View "public.v1"
View "olap_window_seq.v1"
Column | Type | Modifiers | Storage | Description
--------+--------+-----------+---------+-------------
dt | date | | plain |
......
......@@ -3,6 +3,11 @@
--
-- Changes here should also be made to olap_window_seq.sql
-- start_ignore
create schema olap_window_seq;
set search_path to olap_window_seq, public;
-- end_ignore
---- 1 -- Null window specification -- OVER () ----
select row_number() over (), cn,pn,vn
......
SELECT name, setting FROM pg_settings WHERE name LIKE 'enable%';
-- start_ignore
create schema rangefuns_cdb;
set search_path to rangefuncs_cdb, public;
-- end_ignore
DROP TABLE IF EXISTS foo;
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册