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

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!

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.

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.

Related

Make column editiable in pgadmin4

How to unlock the fields in pgadmin4 so I can insert/update column directly threw pgadmin4 Data Output result.
Please refer below image displaying lock icon in each field
I want result like below which has icon of a pencil which shows that the field is editable.
I have given all the permission on the table.
Give your table a primary key column. Otherwise, pgAdmin4 has no way to communicate to the database which row you are trying to edit.
We have to make sure we have selected the primary key at tables properties level (right click on your table).
You can do that inside table properties column section:
It happens if I do a join with me, try seperately running the queries without joins for the columns that you want to edit.

How to filter table name not a database name in Navigator. It seems there's no option for filtering

As you see, it's Database name to filter. There's just few databases. So no need to filter 'Database name`. I need to change it to 'Table name to filter'. But it seems there's no option for it.
Weird thing is, it was a 'Database name to filter' at the time of first installation. I don't know when and how it changed.
Just re-installed it and it's done :(

Database table columns missing in MySqlWorkBench, working with v6.3 so not an upgrade issue

I know that another question of same title exists, but I am new and unable to leave a comment there.
After 6 months of using MySQLWorkBench v6.3, all of a sudden I can no longer edit my table columns.
When I click on the tool icon next to the table name in the scheme, all of the fields I would need to edit for columns are disabled and empty.
I can see my indexes.
I can see my foreign keys.
I can see all the columns listed in the tree under the schema.
But I can't see any columns in the Columns tab for that table.
This just started happening this week. I've tried rebooting, refreshing, and giving my PC some rest and relaxation.
Any other ideas?
The last thing I did in my database was add a foreign key, which was successful. After that, starting having column issue. Not sure if that's a clue or not.

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

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.
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.
Try synchronize database connection. It helped me in mysql connection.
What actually helped was toggling Auto-commit checkbox in console, after that everything runs flawlessly.
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.
This can be due to default settings, make it sure your your transaction Mode settings are as below
I had the same issue with datagrop 2020.2. I have followed all the method but for me, just delete the connection and create new connection (never trying to duplicate) just manual. It is works!
Set and clear Read-only in Data Source Properties helps me.
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
If your query is using field alias (renaming column instead of using actual column name) , then Datagrip set data results as read only.
Solution:
Rewrite query using field names as in the table and rerun query. Then you will be able to edit the rows.
Example
Rewrite this:
select id,interest_recalcualated_on, interest_recalculation_enabled alias from m_loan;
..to this:
select id,interest_recalcualated_on, interest_recalculation_enabled from m_loan;
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.
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.
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.
For me, when I changed back my Select query to * (wild char to select all the columns), from specific columns, the edit and save started to working again. This is strange! May be worth reporting a bug to intellij. I'm using DataGrip 2020.1 on macOs Catalina 10.15.3
I thought I had the same problem but just realized I needed to submit changes (with a button or command + enter) for them to be applied.
This answer is 4 years late though. Maybe the bug was already fixed haha, but this may help someone else.
The problem for me was the obvious (well obvious after identifying it) - using a MySQL keyword as a field name (yes I know its not a good idea but thats how it is sometimes). So this caused the error
select id,name,value from mytable;
The correct way to write this of course is using backticks so:
select id,name,`value` from mytable;
and this solved it for me.
seems like DataGrip doesn't allow to change data in the ui table if you select specific columns with joins.
so if you select table1.column1, table2.column2 from <table1> inner join <table2> and try to change the value in column1, you will receive This table is read only warning
only if you do select * from <table>, you can edit the cell values
try this
In the IDE settings (Ctrl+Alt+S), go to Database | General.
Select the Open results in new tab checkbox and click OK.
Re-run your query, and you'll be able to edit and commit the changes in the new tabs.

Crystal: Autoupdating table names in database expert

It is more of an annoyance rather than real issue: when in Crystal reports you change the data source to one with different name (and do all the linking old columns to new columns) all the table names in Field explorer and (obviously) in formulas are changed. But the Database expert still shows the old table/view name!
Let me show this on example: Lets say I change TABLE_1 with column EQUIPMENT to VIEW_1 with column UNIT. Via the datasource location I can do the substitution and link old column EQUIPMENT to new one - UNIT.
But when I check either Datasource location or database expert it will be still showing old TABLE_1 (if you check the columns in the link tab you will notice that the TABLE_1 has now column UNIT instead of EQUIPMENT).
This can be quite annoying and frankly bit dangerous, especially if you return to report after a longer while. Is there somewhere a setting that allows to autoupdate table names in the database expert?
When you create the report it will create tables and each table will be linked to a datasource table. So the report table will have a name and datasource , which might be the same. When you change the datasource the datasource of the table will be updated but the report table name will remain the same. Think about this name as an alias. It might differs from th datasource name if you use the same table multiple times
I don't think there is auto update option in crystal reports but one thing you can do is to use Verify Database option under Database tab whenever you update the tables.
You need to manually edit table names in Database expert, there's no automatic way (and like Lan already answered, it is generally not possible).