Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot delete rows in grid in SQL Server
See original GitHub issueIf I perform a select, and then I press the del key onto a row, and I click on the green check in order to confirm the changes, I get first a generic message:
Can't detect source entity
and then I get
org.jkiss.dbeaver.DBException: No unique identifier defined
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Cannot delete a row from a table - MSDN - Microsoft
Solution4: This solution is used for instances where you just need to delete one duplicate row. Just use a delete statement like you...
Read more >Cannot Delete Rows From A Temporal History Table In SQL ...
First is to remove the main table's System Versioning option. b. Next is to delete the records of the temporal history table. Delete...
Read more >Unable to delete row from table in Microsoft SQL Server ...
A problem occurred attempting to delete row 1. Error Source: . Net SqlClient Data Provider. Error Message: The select list for the INSERT ......
Read more >Can't Delete Row (Grid editing error) (0 rows ... - HeidiSQL
Can't seem to delete a record. I can do it from a Query with sql but not by right clicking on the record...
Read more >Python MySQL Delete From - W3Schools
Notice the WHERE clause in the DELETE syntax: The WHERE clause specifies which record(s) that should be deleted. If you omit the WHERE...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For me, I refreshed the connection and the problem went away.
It seems that adding
dbo.before the table name fixes the issue. Thanks for support