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

后端 未结 14 2258
北荒
北荒 2020-12-11 00:45

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

相关标签:
14条回答
  • 2020-12-11 01:13

    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.

    0 讨论(0)
  • 2020-12-11 01:18

    What worked for me was removing a field alias - going from this:

    SELECT
      l.MSKU Item_SKU,
      l.Supplier,
      l.ASIN,
      l.title,
      l.Buy_Price
    FROM listings l
    WHERE l.Buy_Price IS NULL
    ORDER BY l.Supplier, l.listingID desc;
    

    to this:

       SELECT
      l.MSKU,
      l.Supplier,
      l.ASIN,
      l.title,
      l.Buy_Price
    FROM listings l
    WHERE l.Buy_Price IS NULL
    ORDER BY l.Supplier, l.listingID desc;
    

    is all it took for me to be able to edit the results of the query

    0 讨论(0)
  • 2020-12-11 01:20

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

    0 讨论(0)
  • 2020-12-11 01:20

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

    0 讨论(0)
  • 2020-12-11 01:22

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

    0 讨论(0)
  • 2020-12-11 01:23

    In my case in version 2020.1 of DataGrip (SQL was run from the opened file, on unique table, so that select just worked as expected, but when I was trying to edit - error appeared: unresolved table reference): specifying schemes in request helped. So that SELECT * FROM users; was changed to SELECT * FROM schemadb.users; and that helped. Probably there is a bug. I've tried all the methods mentioned above.

    0 讨论(0)
提交回复
热议问题