You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/02/12 15:51:00 UTC
[jira] [Commented] (CALCITE-2844) Babel parser doesn't parse
PostgreSQL table function
[ https://issues.apache.org/jira/browse/CALCITE-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16766170#comment-16766170 ]
Stamatis Zampetakis commented on CALCITE-2844:
----------------------------------------------
Same comment as CALCITE-2843. Please, improve a bit the description of the ticket.
> Babel parser doesn't parse PostgreSQL table function
> ----------------------------------------------------
>
> Key: CALCITE-2844
> URL: https://issues.apache.org/jira/browse/CALCITE-2844
> Project: Calcite
> Issue Type: Bug
> Components: babel
> Affects Versions: 1.18.0
> Reporter: Muhammad Gelbana
> Assignee: Julian Hyde
> Priority: Major
> Fix For: next
>
>
> *Query*
> {code:sql}
> SELECT typinput, typtype FROM pg_catalog.pg_type LEFT JOIN (select ns.oid as nspoid, ns.nspname, r.r from pg_namespace as ns join ( select s.r, (current_schemas(false))[s.r] as nspname from generate_series(1, array_upper(current_schemas(false), 1)) as s(r) ) as r using ( nspname )) as sp ON sp.nspoid = typnamespace WHERE typname = $1 ORDER BY sp.r, pg_type.oid DESC LIMIT 1{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)