Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable Inline Editing on result set #6397

Closed
LukasBreit opened this issue Aug 1, 2019 · 5 comments

Comments

@LukasBreit
Copy link

commented Aug 1, 2019

System information:

  • IBM I series 7.2
  • DBeaver version 5.2.4

Connection specification:

  • DB2

Describe your question:

Is it possible to disable inline editing of a result set? Setting the preferences of Double-click behaviour to "None" disables not all the possibilities to edit the result set. If a cell is focused and you start entering some text, you can still change the value. The same is possible by right click on a cell --> Edit --> Inline Edit.
All these options need to be disabled, so that the user can update a table only by using a sql statement, not the result set of a Select statement.

Thanks for help!

@LukasBreit LukasBreit added the question label Aug 1, 2019

@serge-rider

This comment has been minimized.

Copy link
Member

commented Aug 2, 2019

There is no such feature (yet?).
You can make connection read-only but this will prevent any kind of data edit (including execution of UPDATE statements).

Could you say why do you need such non-standard feature?
Maybe we need a feature request for it..

@LukasBreit

This comment has been minimized.

Copy link
Author

commented Aug 5, 2019

We had some problems with the inline-edit.
We have tables without a primary key, so all columns are used by DBeaver for an update on these tables. When someonde did an update via inline-edit, some records have been changed, which shouldn't be changed.
Our assumption is, that the table structure has been changed outside from DBeaver, but DBeaver remembered the old table structure and used this for the update.

Because such errors can create a lot of work for us, we want to disable the feature.

@serge-rider serge-rider added feature request and removed question labels Aug 5, 2019

@serge-rider serge-rider added this to the 6.1.5 milestone Aug 5, 2019

@serge-rider

This comment has been minimized.

Copy link
Member

commented Aug 5, 2019

This makes sense

@tati-kru tati-kru added this to Backlog in DBeaver project Aug 5, 2019

@serge-rider serge-rider moved this from Backlog to In Progress in DBeaver project Aug 9, 2019

serge-rider added a commit that referenced this issue Aug 9, 2019

serge-rider added a commit that referenced this issue Aug 9, 2019

serge-rider added a commit that referenced this issue Aug 9, 2019

serge-rider added a commit that referenced this issue Aug 9, 2019

@serge-rider

This comment has been minimized.

Copy link
Member

commented Aug 9, 2019

We'll make it even better:

image

@serge-rider serge-rider moved this from In Progress to Ready for QA in DBeaver project Aug 9, 2019

@kseniiaguzeeva kseniiaguzeeva self-assigned this Aug 9, 2019

serge-rider added a commit that referenced this issue Aug 11, 2019

@kseniiaguzeeva

This comment has been minimized.

Copy link

commented Aug 11, 2019

Verified.

DBeaver project automation moved this from Ready for QA to Done Aug 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.