datagrip Cannot apply changes This table is read only. Cell editor changes cannot be applied

Question

So simply the problem occurs when I want to edit selected rows and then apply it. I'm sure it worked some time ago. Tried redownload postgres driver in preferences(yeah, I use postgres) Anyone faced same issue? Anyone succeed?

PS. Running on 142.4861.1.

I found read only checkbox in connection preferences, it was not set, toggling didn't help, upgrading, reseting also didn't help.

Answer 1

What actually helped was toggling Auto-commit checkbox in console, after that everything runs flawlessly.

Answer 2

Try synchronize database connection. It helped me in mysql connection.

Answer 3

The only thing that actually worked for me, after trying everything above multiple times, was deleting each DB connection and remaking a new one from scratch.

Answer 4

Set and clear Read-only in Data Source Properties helps me.

Answer 5

Nothing worked. I had to update DataGrip from 2017.2 to 2018.3

I had to open the project by navigating to: /home/user/.DataGrip2017.2/config/projects/my_project/

All my scripts for this project as I did not want to import the config from the old version of Datagrip. So I'll probably need to downgrade, get the scripts and upgrade again.

Answer 6

try this

1. In the IDE settings (Ctrl+Alt+S), go to Database | General.

2. Select the Open results in new tab checkbox and click OK.

3. Re-run your query, and you'll be able to edit and commit the changes in the new tabs.

Answer 7

I struck the same issue, not Postgres but MySql, PhpStorm 2019.1 when I had two schema available on the same db connection and my query: select * from users where full_name like '%handy%'; resulted in a result table that couldn't be edited even though the console reported it was querying the stage schema. A more specific query: select * from stage.users where full_name like '%handy%'; using the exact table name led to a results table that could be inline edited.

Answer 8

The only way I was able to get around this issue was to remove the database connection details for the given connection and recreate them from scratch. While this was happening to me on this specific connection, editing was working fine on other connections, which suggests the problem might be related to specific parameters around the connection in question.