8000 🐛 Bug: Allow Schema Change "client password must be a string" · Issue #11106 · nocodb/nocodb · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

🐛 Bug: Allow Schema Change "client password must be a string" #11106

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
jeremielebot opened this issue Apr 14, 2025 · 2 comments
Closed
1 task done

🐛 Bug: Allow Schema Change "client password must be a string" #11106

jeremielebot opened this issue Apr 14, 2025 · 2 comments

Comments

@jeremielebot
Copy link

Please confirm that the bug report does not already exist

  • I confirm there is no existing issue for this bug.

Steps to reproduce

  1. Go to the Project
  2. Data Source tab
  3. On the remote pgSQL source, click "Actions", "Edit"
  4. Enable "Allow Schema Change"
  5. Click "Test Connection"

Error message :
Connection Failure: SASL: SCRAM-SERVER-FIRST-MESSAGE: client password must be a string

However, if I create a New Data Source, duplicating the existing one and go to the same process. It works. Test connection becomes Test succesful.

But I won't duplicate my connection to circumvent the issue because I would lose views, formating...

Current project and connection predates the "Integration"/"Connection" menu.

Desired Behavior

Being able to edit the schema on my existing connection.

Project Details

NocoDB used as docker: ✅
NocoDB version: 0.262.5
Database used in NC_DB URL: pg
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: linux
Node.js version: v22.14.0
Database version: postgre v14.5

Attachments

No response
@fendy3002
Copy link
Collaborator
fendy3002 commented Apr 18, 2025 •
edited
Loading

Hello @jeremielebot, cannot replicate this issue, is the issue still persists after restarting the server? which database that you need to connect? Can you try to create another connection, then change that 2nd connection and see if this issue still persists?

@jeremielebot
Copy link
Author
jeremielebot commented Apr 23, 2025 •
edited
Loading

The workaround of duplicating the connection, editing in the copy and resync metadata in the main one work. A bit clunky though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fendy3002 @jeremielebot
0