You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please confirm if bug report does NOT exist already ?
I confirm there is no existing issue for this
Steps to reproduce ?
Create a separate schema in the Postgres DB that NocoDB will use (e.g. create schema nocodb). Grant privileges on the schema to the NocoDB user (grant all privileges on nocodb to nocodb_user).
Install NocoDB pointing to a separate schema in Postgres, rather than public. Following the above example, this was accomplished by using ALTER ROLE nocodb_user SET search_path = nocodb;
Create a table in a base.
Attempt to rename table.
It seems that the rename operation is attempting to explicitly look for the table to rename in the public schema. Whereas in this case, the table is in a different schema. Everything else I've used so far appears to work when pointing the DB user's search path to a separate schema, just not table rename.
Please confirm if bug report does NOT exist already ?
Steps to reproduce ?
create schema nocodb
). Grant privileges on the schema to the NocoDB user (grant all privileges on nocodb to nocodb_user
).ALTER ROLE nocodb_user SET search_path = nocodb;
It seems that the rename operation is attempting to explicitly look for the table to rename in the public schema. Whereas in this case, the table is in a different schema. Everything else I've used so far appears to work when pointing the DB user's search path to a separate schema, just not table rename.
Desired Behavior
The table should be renamed.
Project Details
Node: v18.5.0
Arch: x64
Platform: linux
Docker: false
RootDB: pg
PackageVersion: 0.207.1
Attachments
Logs:
The text was updated successfully, but these errors were encountered: