Provide history of executed OQL queries
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
I'm always frustrated when I forget to save my OQL queries.
I think that execution history similar to what SQL tools have would be great feature: https://docs.devart.com/studio-for-mysql/writing-and-executing-sql-statements/query-execution-history.html. I would prefer if the history was not limited or if limited then only by disk size. I assume that the history will be relatively small disk size wise.
Nice to have: if I open a heap dump and OQL console, VisualVM would show history of queries that I've executed against that specific heap dump.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OQL console and trace how queries are executed. Determine how execution history should be stored, whether it is limited by disk size, and how history would be associated with a specific heap dump. Done means the requested history is available when using the OQL console, including the heap-dump-specific behavior if implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100