Read-only: No Corresponding table column

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:

why？

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

@uslss The latest version is not resolved

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

example.zip
@uslss

thanks for the report and clarification

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

Verified

Problems still exist

@uslss @serge-rider

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

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

Extra fix applied. When we have both sub-select and direct column references we must evaluate direct refs and ignore sub-select.

Verified

Good job, I'll test it again when the new version is released.

@uslss @serge-rider @Matvey16
Feedback again, test results.
The previous version of dbeaver-ce-7.2.3-win32.win32.x86_64 tested fine.
dbeaver-ce-7.2.4-win32.win32.x86_64 version started to have problems.
ddl
example2.zip

@yid Have you tried reproducing on the latest 21.1.2 version?

Yes, I did test 21.1.2 the day it was released.
@Matvey16

@serge-rider

@yjd We will work on it, scheduled to be fixed in the next update

Joined tables edit support was added.
@Matvey16 please test it in PG, MySQL and Oracle as well.

Verified for SQL Server PostgreSQL, MySQL, Oracle

The query has joins

@serge-rider  @Matvey16
Feedback
The latest version of dbeaver-ce-21.1.5-win32.win32.x86_64.zip has a problem with the save button not being activated.
dbeaver-ce-21.1.4-win32.win32.x86_64.zip Everything is fine

Same issue here: one nullable column of the result set of a SELECT query is marked as Read-only: no corresponding table column in a writable database.
The column header name has a little dot of the same color of the connection type. Other nullable columns of the same result set are editable. The connection type security restrictions are all unchecked (restrict data edit, restrict structure edit, etc). Modifying the column value through an UPDATE SQL statement works fine.
Refreshing the database connection nor the table properties where the column is located did not fix the issue.
Here is the query (the read-only column is candypluto):
SELECT
    DISTINCT ON (p.id) p.id AS pid,
    c.pippo,
    c.pluto AS candypluto
FROM
    paperino p
    JOIN paperino_sweetcandy psc ON p.id = psc.paperino_id
    JOIN sweetcandy oc ON psc.defaultcandys_id = oc.id
    JOIN candy c ON c.id = oc.candy_id
WHERE
    p.topolino_id = 1
    AND p.status = 'ACTIVE'
    AND c.pluto IS NOT NULL;

Using DBeaver Version <IP_ADDRESS>112111946, on Windows 10 21H1, on a PostgreSQL database.

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.

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.

Worked for me, thanks for sharing @vongohren

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.

Also worked for me 🙌  thanks!

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.

THANK YOU! This worked. I'm connected to a remote MySQL server (PlanetScale). When I added a column to an existing table from the PlanetScale console, it appeared in my table as read only as above.

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.

Same here ! work like a charm, you can go for it if facing the same issue, while it is getting fixed.

I've got this after I updated a table and added a new column. It's gone after I restarted dbeaver.

dbeaver Version <IP_ADDRESS>204190012

saw this in dbeaver 21.3.5 after a column was added to a MariaDB database while DBeaver was open then trying to edit a value in that new column. restarting DBeaver as suggested above fixes the issue. Just wanted to chip in in case thats helpful at all

FYI, it happened to me with this workflow:

Connect to DB
Added a field through Laravel migration
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 bug appears to have returned in some form in version 22.1.1. After adding several columns in one SQL editor, I switched to another editor and ran a "select * from table" query, and the columns came up as "Read only: no corresponding row id". After trying different things, I quit dBeaver and restarted and that fixed the issue.
Steps to reproduce:
ran the following queries in one editor:
ALTER TABLE mytable ADD latitude decimal(9,7) DEFAULT NULL AFTER zip_code;
ALTER TABLE mytableADD longitude decimal(10,7) DEFAULT NULL AFTER latitude;
ALTER TABLE mytable ADD geofence_radius decimal(6,2) DEFAULT 250 NULL AFTER longitude;
switch to second edior and run:
SELECT * from mytable order by id;

I get this on a simple query where I've assigned column names:

FYI, it happened to me with this workflow:

Connect to DB
Added a field through Laravel migration
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

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 ?

efresh the database so DBeaver has every

Getting the same after adding new column with the editor.

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?

Got this bug on DBeaver 22.2.1 for Mint on MariaDB
STR:

Connect to database
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

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.

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

Have the same issue with <IP_ADDRESS>301060755 when trying to edit column of type HSTORE on PostgreSQL 12 and 14.

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.

@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 ...

Getting this as well on Version <IP_ADDRESS>301211053 .
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.

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

Database disconnect/connect should work too.
Currently DBeaver doesn't refresh database metadata when you execute DDL queries in SQL editor.

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'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

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");

+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.

if you do select * from table seems to work.
select column1, column2,... from table seems to have the issue.

Your milage may vary, but we're using Aurora and had it set as MariaDB. I found https://github.com/dbeaver/dbeaver/issues/18756 and followed that to change the driver to MySQL and it's working now

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;

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.

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
https://github.com/dbeaver/dbeaver/issues/11891#issuecomment-1575596102,
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.

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.

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

This is still an issue in Version <IP_ADDRESS>309041200, on a simple query of SELECT * from this_table.

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

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:

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	<IP_ADDRESS>309040911	org.jkiss.dbeaver.ide.feature.feature.group	JKISS
connected to mysql 5.5 (I know)


Support callbacks with then/nodeify module

I'm not trying to be "that guy" but as a long time consumer of this module I'm not upgrading to the 1.0 branch because of the move away from standard callbacks to Promises. I understand the aesthetic and flow control benefits gained, however, the public API should follow the best practices of the community. I shouldn't have to work around your internal design choices.
Please consider providing a dual API until Promises are standardized in the Javascript/Node community. Since you are using the then/promise module, might you also consider their https://github.com/then/nodeify module to integrate callback support?

Promises are a standard part of JavaScript as of ES6, they're implemented in browsers, and will be in Node.js (and are in the IO.js fork). The switch to using Promises reduced the LOC by 1/3, made this package faster, and made the code easier to read.

I'm not asking for you to remove Promise support, simply to provide both callbacks and Promises in your public facing API. While, yes, Promises are the future of handling async code, the future is still the future. They are not currently present in Node stable and ES6 is still a working draft — thus the reason you are depending on the then/promise module. Can you provide benchmarks for the speed claims?


Add ChainRule for keyless_unname

Essentially pair-programmed with @mzgubic.
Needed to add an rrule for keyless_unname for a downstream AD use-case.

orthogonal to the changes I am adding here

I should look closer but _KeyedArray_pullback(ȳ::AbstractArray, keys) = (NoTangent(), wrapdims(ȳ, keys...)) looks like it wants to attach key vectors to the gradient. I'm not sure that's a good idea. Their values are part of the original x, not its gradient. Can't it just stay an array?

orthogonal to the changes I am adding here

I should look closer but _KeyedArray_pullback(ȳ::AbstractArray, keys) = (NoTangent(), wrapdims(ȳ, keys...)) looks like it wants to attach key vectors to the gradient. I'm not sure that's a good idea. Their values are part of the original x, not its gradient. Can't it just stay an array?

Ah I see, yeah that makes sense. I've changed it to return an array and refactored the code to be more simple.

bump

bump

@glennmoy  tests are failing

fixed

bump


[AutoPR consumption/resource-manager] [Hub Generated] Review request for Microsoft.Consumption to add version 2019-01-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5311

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2158


Django 4.0+ compatibility

as soon as I add to base.py this:
INSTALLED_APPS += [
   'debug_toolbar',
]

I get ImportError: cannot import name 'url' from 'django.conf.urls'
apparently django.conf.urls.url() was deprecated in Django 3.0, and is removed in Django 4.0+
is there any way to make Django Debug Toolbar work in Django 4.0+?

What version of the toolbar are you using? Please share the full stacktrace.
On Tue, Mar 8, 2022, 6:04 AM Salomanuel @.***> wrote:

as soon as I add to base.py this:
INSTALLED_APPS += [
'debug_toolbar',
]
I get ImportError: cannot import name 'url' from 'django.conf.urls'
apparently django.conf.urls.url() was deprecated in Django 3.0, and is
removed in Django 4.0+
is there any way to make Django Debug Toolbar work in Django 4.0+?
—
Reply to this email directly, view it on GitHub
https://github.com/jazzband/django-debug-toolbar/issues/1593, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJYZP6P2CJPRAGRFT7RQ63U6465NANCNFSM5QGEX5FQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'm very sorry, being new to Python and Wagtail I was following a tutorial (wagtail-for-beginners) and it was forcing  django-debug-toolbar==2.1
once I changed it to a current version, the problem got fixed
I'm very sorry for wasting your time!

No worries, we've all been there and run into that scenario. Best of luck
to you!
On Tue, Mar 8, 2022, 7:21 AM Salomanuel @.***> wrote:

Closed #1593
https://github.com/jazzband/django-debug-toolbar/issues/1593.
—
Reply to this email directly, view it on GitHub
https://github.com/jazzband/django-debug-toolbar/issues/1593#event-6202442167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJYZP3EDF66Z2PNQKIE2G3U65H7BANCNFSM5QGEX5FQ
.
You are receiving this because you commented.Message ID:
@.***
com>