Read-only: No Corresponding table column

[yjd]

Starting in 2020, there has been this problem from a certain version of 7.2 to the latest version 7.3:
Read-only: No Corresponding table column
screenshot:

Version 7.2 does not have this problem before September 2020,
screenshot:

[yjd]

why？ @serge-rider

[uslss]

@yjd sorry for the late response
could you check if the issue is reproducible for you against 21.0.3?

[yjd]

@uslss The latest version is not resolved

[uslss]

@yjd what database do you use? probably you could provide table(s) DDL and query example? It will be very useful for issue investigation

[yjd]

example.zip
@uslss

[uslss]

thanks for the report and clarification

[serge-rider]

The problem is caused by sub-selects. SQL Server doesn't provide meta information + we don't support sub-selects in query parser.

Fixed

[Matvey16]

Verified

[yjd]

Win2008R2 + Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64)

Problems still exist

@uslss @serge-rider

[yjd]

@uslss @serge-rider
In version 7.2 before September 2020, there is no such problem. What is the reason? Thanks!

[Matvey16]

Reopening this issue. Reproduced this not only with sub-select but also with a likewisejoin query.

[umangjun92]

FYI, it happened to me with this workflow:

1. Connect to DB
2. Added a field through Laravel migration
3. Refresh the table view through F5. Field is appearing correctly but has the Read only tag

I simply had to refresh the database so DBeaver has everything to display the table correctly

This worked for me

[bombillazo]

Im still getting this and the way I have to solve this is to hit refresh on the properties page to get the column represented there.

Hey, this is still an issue for me, what properties page ?

[rgimenes26]

efresh the database so DBeaver has every

Getting the same after adding new column with the editor.

[MikeB2019x]

I'm curious: why would refreshing the database be expected to influence the results/display of a query? The db hasn't changed, it has just been queried, correct? Or is there a deeper SQL effect taking place?

[rovvit]

Got this bug on DBeaver 22.2.1 for Mint on MariaDB

STR:

1. Connect to database
2. Run ALTER TABLE table_name ADD column_name

Newly added column is marked as read-only

How 2 fix: refreshing the table (via F5) worked for me

[X-lem]

Just noticing this as well. Using PostgreSQL 14. Just updated my DBeaver to 22.3.0 (noticed it on 22.2.x and did a restart/upgrade to see if that would reslove it).

Seems to only be happening on columns with the type citext

Table for reference:

CREATE TABLE IF NOT EXISTS Users
(
  ID SERIAL NOT NULL PRIMARY KEY,
  UUID uuid NOT NULL DEFAULT uuid_generate_v4(),
  Username citext UNIQUE NOT NULL,
  Password varchar(255) NOT NULL,
  ForcePasswordUpdate BOOL NOT NULL DEFAULT TRUE,
  Email citext UNIQUE,
  EmailVerified BOOL NOT NULL DEFAULT FALSE,
  KleiID CHAR(11) UNIQUE,
  AllowGroupInvites BOOL NOT NULL DEFAULT TRUE,
  IsSiteAdmin BOOL NOT NULL DEFAULT FALSE,
  LastLogin TIMESTAMP,
  DateCreated TIMESTAMP NOT NULL DEFAULT NOW(),
  DateArchived TIMESTAMP
);

Oddly enough, I happened to have an old instance of PostgreSQL 12 laying around. I can update citext fields on that just fine.

Edit: Hitting refresh on the properties page didn't solve the issue for me.

[skharab-anaplan]

Had the same issue with one of the varchar column, fixed with 22.3.0 update. Thanks.

[gkresic]

Have the same issue with 22.3.2.202301060755 when trying to edit column of type HSTORE on PostgreSQL 12 and 14.

[hheg]

Hi! I'm seeing this as well. The reason for this seems like that the red dot shows up when there's an inconsistency between the Database navigator field and the result set where the red dot is showing. So if the result set is showing more columns than what the Database navigator is showing the red dot is indicating this on those missing columns in the result set. If you refresh the table in the Database navigator the red dot in the result set disappears. I believe this is intended. I'm using DBeaver 22.2.4.

[Donal-Goggin]

I'm getting this as well on 22.3.3. It's behaving very strangely

select * from table1; - Execute statement on this returns that table and it's editable

#random line comment
/*random block comment*/
select * from table1;

Executing this query with the comments above it returns a read-only table with every column having the "No Corresponding table column" error. A yellow lock icon also appears in the top left

This was fine last week so something must have changed. Is there any news on a fix?

[MikeB2019x]

@serge-rider There are 22 comments since this issue was closed indicating this issue isn't resolved. Maybe it's time for contributors to post something about why it isn't seen as a problem if only to provide a definitive answer to this? Please.

Examples:

• Issue duplicate of ...
• Issue solved by ...
• Issue caused by ... and no further action will take place because ...

[emgdenis]

Getting this as well on Version 22.3.3.202301211053 .

As per @Donal-Goggin suggestion, removing the comments from the query has "unlocked" the result and was able to edit the columns.

Very strange behaviour as this wasn't an issue on the previous version.

[curVV]

Same issue here, on version 22.3.3.202301211053. Refreshing the database or the table/column did NOT work for me. Only thing that worked was restarting dbeaver.

[serge-rider]

Database disconnect/connect should work too.

Currently DBeaver doesn't refresh database metadata when you execute DDL queries in SQL editor.

[mrladeia]

I'm having this problem when I updated dbeaver to version 22.3.4, before that I ran the same code SQL in version 22.3.3 and didn't have this problem.

I'm using PostgreSQL 12

[mrladeia]

I'm having this problem when I updated dbeaver to version 22.3.4, before that I ran the same code SQL in version 22.3.3 and didn't have this problem.

I'm using PostgreSQL 12

I downgraded to version 22.3.2 and it solved the problem. (Windows 10 x64) (dbeaver-ce-22.3.2-x86_64-setup.exe)

https://github.com/dbeaver/dbeaver/releases/tag/22.3.2

[mrladeia]

I'm having this problem when I updated dbeaver to version 22.3.4, before that I ran the same code SQL in version 22.3.3 and didn't have this problem.
I'm using PostgreSQL 12

I downgraded to version 22.3.2 and it solved the problem. (Windows 10 x64) (dbeaver-ce-22.3.2-x86_64-setup.exe)

https://github.com/dbeaver/dbeaver/releases/tag/22.3.2

Select example:
In this SQL the problem occurs: select *, te.column_date+ INTERVAL '1 month' from table_example te where "user" in('x','y') order by lower("column");

Here the problem does not occur: select * from table_example te where "user" in('x','y') order by lower("column");

[QAnders]

+1

So annoying... None of the given trix here work, refresh or disconnect/connect it's still in Read-Only for 22.3.4.

Followed @mrladeia's suggestion and downgraded to 22.3.2 which fixes the issue.

[PorphyriusSoftware]

if you do select * from table seems to work.

select column1, column2,... from table seems to have the issue.

[jaylyn5554]

Running v22.3.4 on an Oracle database and I am getting the same problem. SELECT * results can be modified, but selecting each column in a table results in the columns being read-only.

[aronduby]

Your milage may vary, but we're using Aurora and had it set as MariaDB. I found #18756 and followed that to change the driver to MySQL and it's working now

[Donal-Goggin]

Still no update here? I'm still finding this bug and now it's even happening for simple queries and I can't work around it
E.G.
select * from table where id = 1234;

[mrladeia]

Still no update here? I'm still finding this bug and now it's even happening for simple queries and I can't work around it E.G. select * from table where id = 1234;

@Donal-Goggin What version of dbeaver are you using? What database and driver are you using?

I think because this issue is closed it is not being monitored. I will create a new issue referencing this one.

[jaylyn5554]

On 04/06/2023 10:46 a.m., Marcos Rodrigo Ladeia wrote: Still no update here? I'm still finding this bug and now it's even happening for simple queries and I can't work around it E.G. select * from table where id = 1234; @Donal-Goggin <https://github.com/Donal-Goggin> What version of dbeaver are you using? What database and driver are you using? I think because this issue is closed it is not being monitored. I will create a new issue referencing this one. — Reply to this email directly, view it on GitHub <#11891 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6ESXG46ELVD2GXJGJ33EQ3XJSNUHANCNFSM4Z24HULQ>. You are receiving this because you commented.Message ID: ***@***.***>

My problem was resolved when I upgraded the version running on my desktop PC to 23.0.  I never had the problem on my laptop, so I am sticking with V22.3.4 on that machine.

[givihuda]

I had to recreate and repopulate the table to fix it... not sure why it started to begin with or how else to fix it.

[matoriazis]

go to "Properties Tab", and refresh the structure on the right bottom corner, maybe it help! it worked for me

[Pareech]

This is still an issue in Version 23.2.0.202309041200, on a simple query of SELECT * from this_table.

[Banack]

As incredible as it seems, I solved it by deleting the comment above the query

[emgdenis]

I encountered the problem only when I had comments like " #comment ". Changing it to " -- comment " doesn't give me any problems. Hope it helps someone...

Example:

[jjd59]

emgdenis solution to change the comment from # to -- worked for me as well. Seems like this should be fixed.
my details:
Eclipse IDE for PHP Developers (includes Incubating components)
Version: 2023-06 (4.28.0)
Build id: 20230608-1333
eclipse plugin DBeaver IDE 23.2.0.202309040911 org.jkiss.dbeaver.ide.feature.feature.group JKISS
connected to mysql 5.5 (I know)