15

I am using DBeaver on Mac and suddenly can't edit/udpate anything on results cell, I get this message:

Column "columns name' is read-only: No corresponding table column.

However, when I use UPDATE command it works just fine.

The challenge is that I have multiple updates to make and it is very convenient to do it ib the results cells.

Other users still can do it and I am suspecting this is something related to my DBeaver client

Any thoughts? Thank you!

RiggsFolly
  • 93,638
  • 21
  • 103
  • 149
RedaB
  • 171
  • 1
  • 1
  • 5

13 Answers13

15

I have faced the same issue, when added a column from script and tried to update data on table from UI. it can solved by disconnecting and connecting to database as DBeaver currently don't refresh the DDLs.

Dhanunjay Mamidi
  • 159
  • 2
7

Incase you created a new table and the cells won't update, DBeaver didn't probably refresh the table you created. In that case all you have to do is click refresh option in sidemenu

Chaandha Raghav C
  • 77
  • 1
3

Same issue here, solved after ommiting rowid as column in then select clause. It appears to be a conflict betwween named an * as column selector in 22.3.3 version. Try to use only * or name explicitly selected columns.

A. Martínez
  • 31
  • 2
2

Thank you all for your feedback and suggestions. Unfortunately, Nothing has worked from the suggested solutions or it was a way too much work to fix this issue.

I downgraded to Version 22.2.2 and everything works perfectly again.

Thank again!

RedaB
  • 171
  • 1
  • 1
  • 5
2

As SKIFO mentioned, refreshing the table works. You can do it from the left menu.

dbeaver screenshot

Jagan Pandurangan
  • 49
  • 5
1

Just had the same issue, what fixed it for me was refreshing the table in the database navigator, really weird though, before the last update I never encountered this

SKIFO
  • 11
  • 2
  • As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Aug 03 '23 at 05:50
0

Faced the same problem. Update to version 23.0.1 helped.

Alexey Bykov
  • 1
0

This is really dumb. I fixed it by deleting comment from script body

Keith
  • 1
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Apr 13 '23 at 07:33
0

I had to expand the columns of the affected table and then refresh while right clicking one of the columns. Just right clicking and refreshing the left side wasn't sufficient. DBeaver 22.3.2 Windows.

hcammidge
  • 43
  • 2
  • 6
0

I'm using mysql in Dbeaver. I had the check the below two configurations

  1. Read table metadata (unique keys)
  2. Read table references (foreign keys)

enter image description here

Sivaraman
  • 168
  • 1
  • 7
  • I already have these checked. Somehow it seems me trying to run an invalid MySQL query (putting a SELECT inside of an INSERT in an intuitive but incorrect way) set the columns for the table to read-only, and then caused a Java crash. Refreshing hasn't helped, restarting hasn't, and I already have those checkboxes checked. – SteveExdia Jul 05 '23 at 16:50
0

Just close the DBeaver and restart it. Hope it will fix this

Shafin Junayed
  • 29
  • 6
0

In my case, I had a comment (with a # not --) right above the query. For some weird reason(maybe there's an explanation idk), when I insert an empty line between the comment and my SELECT query it doesn't give me this message and allows me to make edits in the binary editor.

NOTE: Based on observation in my intel mac, with DBeaver Version 23.1.5.

Looks like this is reported on github: https://github.com/dbeaver/dbeaver/issues/18851#issuecomment-1408289013

edit1: Add Github link

edit2: clarify comment message type

Vijay prasath
  • 36
  • 3
0

Just head over to Database Navigator in the left pane.

Click on the connection the table that you've altered is associated with.

Navigate to Databases > your-database-name > Schemas > public > Tables

Right click the table and hit Refresh.

Now, re-run the select query.

This solved the problem for me.

PS: If, this didn't work for you, try refreshing the specific column that you've made changes to.

Vishnu Thulasidoss
  • 1
  • 2