Commit 48e1a399 authored by Bruce Momjian's avatar Bruce Momjian

I guess the intention was to test incomplete SELECT statements, not

missing semicolons.

I also added a SELECT statement without a target list.

Manfred Koizar
parent 92a162c0
......@@ -2,7 +2,12 @@
-- ERRORS
--
-- bad in postquel, but ok in postsql
select 1
select 1;
?column?
----------
1
(1 row)
--
-- UNSUPPORTED STUFF
......@@ -16,10 +21,14 @@ select 1
-- RETRIEVE
-- missing relation name
select
select;
ERROR: parser: parse error at or near ";" at character 7
-- no such relation
select * from nonesuch;
ERROR: parser: parse error at or near "select" at character 10
ERROR: Relation "nonesuch" does not exist
-- missing target list
select from pg_database;
ERROR: parser: parse error at or near "from" at character 8
-- bad name in target list
select nonesuch from pg_database;
ERROR: Attribute "nonesuch" not found
......
......@@ -3,7 +3,7 @@
--
-- bad in postquel, but ok in postsql
select 1
select 1;
--
......@@ -20,11 +20,13 @@ select 1
-- RETRIEVE
-- missing relation name
select
select;
-- no such relation
select * from nonesuch;
-- missing target list
select from pg_database;
-- bad name in target list
select nonesuch from pg_database;
-- bad attribute name on lhs of operator
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment