Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sql: clarify the existence of function namespaces and expose the resolution rules #13283

Closed
7 of 8 tasks
knz opened this issue Jan 30, 2017 · 1 comment
Closed
7 of 8 tasks
Assignees
Milestone

Comments

@knz
Copy link
Contributor

knz commented Jan 30, 2017

This issue is a combined docs+engineering request:

  • add an explanation on function and table name resolution in SQL docs - Tell a bit more about SQL name resolution. docs#1050
  • add doc pages that explain the special namespaces: crdb_internal, pg_catalog etc
  • add a feature to configure the namespace search (SET) and document it
  • move pg-specific functions (e.g. unnest, format_type) to ns pg_catalog where they belong
  • move standard SQL functions to ns sql where they belong -- then extend the standard search path to include sql
  • upgrade the function doc page generator to produce function tables per namespace
  • produce a common function list that includes the "promoted" functions -- all those from namespace sql plus some from pg_catalog.
    • add a mechanism to annotate pg_catalog functions as being "promoted" and use that in the generator.

cc @jseldess

@knz knz self-assigned this Jan 30, 2017
@cuongdo cuongdo added this to the Later milestone Feb 22, 2017
@knz
Copy link
Contributor Author

knz commented Jun 7, 2017

This has been more or less thoroughly addressed already.

@knz knz closed this as completed Jun 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants