Skip to content

Change HAS_DBACCESS() to always return 1. - #1

Open
rossd-bitquill wants to merge 4 commits into
BABEL_1_X_DEVfrom
fix_has_dbaccess
Open

Change HAS_DBACCESS() to always return 1.#1
rossd-bitquill wants to merge 4 commits into
BABEL_1_X_DEVfrom
fix_has_dbaccess

Conversation

@rossd-bitquill

Copy link
Copy Markdown
Owner

Description
The existing HAS_DBACCESS() implementation always returned NULL due to an exception thrown by the Psql call, because the Babelfish table names do not agree with the Postgres table names.

This is a temporary change to the HAS_DBACCESS() procedure to always return 1. Expected functionality will be implemented along with a larger piece of work to implement the permissions/ownership of tables and databases in Babelfish.

Issues Resolved
None

Check List
[ X ] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

rossd-bitquill and others added 4 commits January 27, 2022 17:39
The existing implementation of HAS_DBACCESS() would always return NULL due to an exception thrown by the underlying psql call because the Babelfish table names do not match the postgres table names.  This commit changes HAS_DBACCESS to always return 1. The underlying issue will be fixed alongside a larger implementation of permissions/ownership.

Signed-off-by: rossd-bitquill <rossd@bitquilltech.com>
Signed-off-by: rossd-bitquill <rossd@bitquilltech.com>
Signed-off-by: rossd-bitquill <rossd@bitquilltech.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant