aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-09-10 14:53:10 +0000
committerBruce Momjian <bruce@momjian.us>2001-09-10 14:53:10 +0000
commitd70a944e0a54a08586ec8296d9abaf7cb52a9db2 (patch)
treeae9484a2a0fffaf57546f87fc01f4006316052d3 /src/backend/parser/parse_expr.c
parentbe18a49d394d106aa1a06d1d8da59327e85be107 (diff)
downloadpostgresql-d70a944e0a54a08586ec8296d9abaf7cb52a9db2.tar.gz
postgresql-d70a944e0a54a08586ec8296d9abaf7cb52a9db2.zip
Bug #1: attribute name when column is type cast:
Given the following table: test=# \d f Table "f" Column | Type | Modifiers --------+---------+----------- i | integer | test | text | If I do the following: test=# insert into f values(1,'test'); INSERT 139549 1 test=# select i::int8,test from f; ?column? | test ----------+------ 1 | test (1 row) It doesn't make much sense that the first column should be called '?column?'. The patch results in the output appearing like this: test=# select i::int8,test from f; i | test ---+------ 1 | test (1 row) ---------- Gavin Sherry
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions