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

CDB_ColumnNames should honor regclass #122

Closed
rochoa opened this issue Aug 24, 2015 · 3 comments · Fixed by #131
Closed

CDB_ColumnNames should honor regclass #122

rochoa opened this issue Aug 24, 2015 · 3 comments · Fixed by #131
Assignees
Labels
Milestone

Comments

@rochoa
Copy link
Contributor

rochoa commented Aug 24, 2015

CDB_ColumnNames current implementation returns columns for any table matching the name.

When having multiple tables with same name but in a different schema it will report the column name from all the tables.

regclass should be considered when providing qualified table names.

@rochoa rochoa added the bug label Aug 24, 2015
@iriberri
Copy link
Contributor

SB/6362235

@javisantana
Copy link
Contributor

why not using the oid so we don't need to add a filter by schema?

@iriberri CDB_ColumnNames is not public api, ping the user about this.

@rochoa
Copy link
Contributor Author

rochoa commented Aug 24, 2015

You are right, actually the signature is CDB_ColumnNames(REGCLASS) so it should be a bugfix more than a new feature as it's already possible to do:

select CDB_ColumnNames('foo.table_name');
select CDB_ColumnNames('bar.table_name');

@rochoa rochoa changed the title CDB_ColumnNames should accept schema filtering CDB_ColumnNames should honor regclass Aug 24, 2015
@rochoa rochoa self-assigned this Aug 25, 2015
@rochoa rochoa added this to the Malpica milestone Aug 31, 2015
@rochoa rochoa mentioned this issue Sep 2, 2015
@rochoa rochoa modified the milestones: Torrelodones, Malpica Sep 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants