I think it's time to make decision what to do with the wiki.
* wiki.phpmyadmin.net is currently read only due to excessive vandalism
which was hard to block
* Mediawiki currently running wiki.phpmyadmin.net is no longer security
* all content pages were copied to GitHub wiki 
* I'm slowly going through wiki pages and integrate that to our user
documentation if it fits there
* bring Mediawiki on wiki.phpmyadmin.net back to usable state
- we will have to handle security fixes and so on
- need some way to prevent vandalism
* use wiki on GitHub
- it's for free with the repository
- the wiki is quite limited (no categories, no search, ...)
- having wiki content as Git repository is great
* use other solution for wiki.phpmyadmin.net
- we could use cleaned up wiki content which is currently used on GitHub
- I'd really prefer something with Git integration
- preferably use GitHub authentication, so that we do not have to
maintain another list of users
- one of possible tools to do that is ikiwiki
I don't think that maintaining Mediawiki is way to go. From remaining
choices I slightly prefer using wiki on GitHub as it needs no
maintenance from us, however it limits wiki features.
Please share your opinion.
Michal Čihař | http://cihar.com/ | https://weblate.org/
This is Pranavan. Few weeks before I started examining phpMyAdmin code and I found and opened few bugs in issue tracker forum. Also I have contributed in two bug fixes as well.
This time I come up with a new feature which I feel, would be a really helpful feature to the frequent phpMyAdmin users who use phpMyAdmin for their all querying needs.
Earlier I thought there is no way to record the query history in phpMyAdmin and then after a good amount of surfing, I found and got to know about pma_history relation residing under phpMyAdmin database.
But still I feel it's not much user friendly because whenever we want to know what queries we issued recently and to re-execute the same queries(for select queries), we always want to go to this particular pma_history table, copy the query and then comeback to the place where we are working, paste and execute which is little troublesome for the user. I myself found it difficult many times to do this continuously.
A research by Mark Sanderson and Susan Dumais on"Examining Repetition in User Search Behavior" found that 33% of user queries were repetitions of queries previously issued by the same user. This not only applicable for web surfing but also for database querying required in other applications as well.
Therefore it's better to have an easy way to access the history of the past queries and further having a way to directly re-execute an already executed select query.
I suggest to have an additional tab in table level and DB level GUI of phpMyAdmin by clicking which user will be able to view and further re-execute (if he/she needs to) a past query again easily(If it is possible).
I have already started working on this feature and this mail is to discuss whether what I feel is feasible and to get suggestions from you all.
Please support and suggest me any ideas related to this.
Thanks and Best Regards,
Third year Computer Engineering,
University of Peradeniya,
I've just upgraded error reporting server (and GitHub hooks) to PHP 7.
It should work just fine, but in case you spot something weird, please
let me know.
Michal Čihař | https://cihar.com/ | https://weblate.org/