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

Global persistent statement history feature request #178

Closed
stoty opened this issue Jan 29, 2016 · 5 comments
Closed

Global persistent statement history feature request #178

stoty opened this issue Jan 29, 2016 · 5 comments
Assignees
Milestone

Comments

@stoty
Copy link

stoty commented Jan 29, 2016

One feature that I found very useful in Workbench, and is not yet available in DBeaver is the global execution history feature.

What I would like to see compared to the current execution log feature is a persistent history that

  • contains the full text of the statement and the execution date
  • including generated DDL statements
  • maybe contains the DB connection and active DB that it was issued on
  • History is stored by eclipse/DBeaver installation, and can be carried over in case of reinstall
  • Independent of the mysql script that issued it
  • can be browsed by date ( like in Workbench)
  • maybe can be searched by regex/glob/sql like
@badloop
Copy link

badloop commented Jul 5, 2017

Is there a status update on this? Persistent history is key especially when queries are constantly changing in your workload and saved queries aren't nearly as beneficial.

@serge-rider serge-rider added this to the 4.2.0 milestone Jul 7, 2017
@serge-rider
Copy link
Member

DBeaver EE already has persistent queries history (in QMDB database). But it still doesn't have UI for it.
Probably will be added in 4.2 version.

@tati-kru tati-kru modified the milestones: 4.3.0, 4.2.0 Sep 10, 2017
@tati-kru tati-kru modified the milestones: 4.3.0, 4.2.5 Oct 28, 2017
@serge-rider serge-rider modified the milestones: 4.2.5, 4.3.0 Nov 12, 2017
@serge-rider serge-rider modified the milestones: 4.3.0, 4.3.1 Dec 15, 2017
@serge-rider serge-rider modified the milestones: 4.3.1, 4.3.3 Dec 27, 2017
@tati-kru tati-kru modified the milestones: 4.3.3, 4.3.5 Jan 20, 2018
@kruger5050
Copy link

Do you guys have any idea when this is implemented? Would be a very nice feature.

@serge-rider
Copy link
Member

We plan to do it in 4.3.5 but honestly I'm not sure.
We have too many FRs at the moment..

@serge-rider serge-rider modified the milestones: 4.3.5, 5.0.1 Feb 17, 2018
@tati-kru tati-kru modified the milestones: 5.0.1, 5.0.3 Mar 21, 2018
@serge-rider serge-rider modified the milestones: 5.0.3, 5.0.5 Apr 18, 2018
serge-rider added a commit that referenced this issue May 6, 2018
serge-rider added a commit that referenced this issue May 6, 2018
serge-rider added a commit that referenced this issue May 6, 2018
@serge-rider
Copy link
Member

serge-rider commented May 8, 2018

First implementation (basic search + filtering by query types and object types) will be added in 5.0.5.
It allows to search in all past queries including implicit metadata requests made by DBeaver.

Further improvements will be done in separate tickets.

Note: query history persistence is supported only in EE version (it is kept in embedded H2 database, this is one of the very few differences between CE and EE). In CE this feature works only for queries executed during current DBeaver session.
CE users still may use "Save log to file" option (this is old feature).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants