phpmyadmin / phpmyadmin/phpmyadmin
History tab
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7.9k
- Forks
- 3.6k
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 36
Description
Is your feature request related to a problem? Please describe.
I miss the tab where I can check all queries written/generated in PhpMyAdmin with option to undo some queries like UPDATE, INSERT or DELETE.
Describe the solution you'd like
Adding History tab where is list of all queries from last N-days generated or written by hand in PhpMyAdmin for specific table (with query, user who generate/written query and date execute of query). Also adding to settings option how long queries have to be remembered.
History can be saved in phpmyadmin table.
It is worth remembering such basic things as:
- Pagination (for example. 10-15 entries on page)
- Collapsed queries by default
- I guess that it's worth add option to disable history for
SELECTqueries because many of them is generated automatic during using PhpMyAdmin (and them can't be undo) - I think that undo the query should be written in history, because "undo" is only generating query which is opposite to query. For example undo for
INSERT:
INSERT INTO `table` (`id`, `col1`, `col2`) VALUES (1, 'a', 'b')
is:
DELETE FROM `table` WHERE `id`=1
Undo forUPDATE:
UPDATE `table` SET `col1` = 'c' WHERE `id`=1
is:
UPDATE `table` SET `col1` = 'a' WHERE `id`=1
Undo forDELETE:
DELETE FROM `table` WHERE `id`=1
is:
INSERT INTO `table` (`id`, `col1`, `col2`) VALUES (1, 'a', 'b')
Probably at the beginning is good to use PRIMARY KEY in undo's (and requirining PRIMARY KEY in table to undo's)
Describe alternatives you've considered
I don't have idea
Additional context
- phpMyAdmin version: N/A
I wanna work on this feature if there are no contraindications to adding such a feature
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
No files, tests, or entry points are named. Start by reviewing the requested History tab, retention settings, phpmyadmin-table storage, pagination, and undo behavior; done would require agreeing on the scope and implementing the specified history and undo workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php
- Domain
- database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100