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
NocoDB used as docker : true
NocoDB version :
Node: v12.22.6
Arch: x64
Platform: linux
Docker: true
Database: pg
ProjectOnRootDB: false
RootDB: sqlite3
PackageVersion: 0.84.12
Project was created by clicking : New Project by connecting to external database
Database on which spreadsheet is created : pg
OS on which NocoDB is running : Fedora 35 KDE
Database version : Postgres 10
Steps To Reproduce
I am trying to connect nocoDB to postgre in a schema with searchPath. It works fine with the postgres account with dbeaver. But under nocodb, if I use a user account with all rights (in database, schema, table creation), I can't create a table and see it:
under dbeaver, the user noco_u is created with all rights on the schema "nocodb" in PG.
under nocodb, creation of the project (with "searchPath": ["nocodb"], )=> connection ok, no table present.
under nocodb, table creation => error : "create table failed" ; table not visible in noco but created in PG.
under PG (dbeaver), creation of 2 tables with the noco_u and postgres account : table created
=> the 2 tables are not visible in nocoDB.
delete the project and create a new project. => the 2 tables are visible in Noco, but not the table created via nocodb.
Could you help me to understand why I cannot manage my table with PG users?
If I create a new project with postgre account, table can be created. But I can not use postgres account that give too much access to database.
** sql PG scritp **
CREATE ROLE inc_r_nocodb WITH INHERIT CONNECTION LIMIT -1;
CREATE ROLE inc_nocodb WITH password 'nocoDBPW' CREATEDB INHERIT LOGIN CONNECTION LIMIT -1 in role inc_r_nocodb;
CREATE SCHEMA nocodb AUTHORIZATION inc_r_nocodb;
with nocodb under pg
CREATE TABLE nocodb.table_user_1 (
id varchar NULL,
titre varchar NULL
);
with postgres under pg
CREATE TABLE nocodb.table_postgres_2 (
id varchar NULL,
titrepg varchar NULL,
valeur numeric NULL
);
Expected behavior
Create new table under NocoDB and manage them with user (not postgres account);
Manage new table created under PG.
Screenshots
If applicable, add screenshots to help explain your problem.
@Chti-Steph Could you try using latest NocoDB release. If issue persists, we will be glad to help. Closing, as this was observed in very older release of NocoDB.
Please enter the following details
NocoDB used as docker : true
NocoDB version :
Node: v12.22.6
Arch: x64
Platform: linux
Docker: true
Database: pg
ProjectOnRootDB: false
RootDB: sqlite3
PackageVersion: 0.84.12
Project was created by clicking : New Project by connecting to external database
Database on which spreadsheet is created : pg
OS on which NocoDB is running : Fedora 35 KDE
Database version : Postgres 10
Steps To Reproduce
I am trying to connect nocoDB to postgre in a schema with searchPath. It works fine with the postgres account with dbeaver. But under nocodb, if I use a user account with all rights (in database, schema, table creation), I can't create a table and see it:
=> the 2 tables are not visible in nocoDB.
Could you help me to understand why I cannot manage my table with PG users?
If I create a new project with postgre account, table can be created. But I can not use postgres account that give too much access to database.
** sql PG scritp **
CREATE ROLE inc_r_nocodb WITH INHERIT CONNECTION LIMIT -1;
CREATE ROLE inc_nocodb WITH password 'nocoDBPW' CREATEDB INHERIT LOGIN CONNECTION LIMIT -1 in role inc_r_nocodb;
CREATE SCHEMA nocodb AUTHORIZATION inc_r_nocodb;
with nocodb under pg
CREATE TABLE nocodb.table_user_1 (
id varchar NULL,
titre varchar NULL
);
with postgres under pg
CREATE TABLE nocodb.table_postgres_2 (
id varchar NULL,
titrepg varchar NULL,
valeur numeric NULL
);
Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Join our discord : https://discord.gg/5RgZmkW for realtime help.
The text was updated successfully, but these errors were encountered: