I'd like to see a dry run feature. A way to show affected rows without actually affecting them. As a newbie developer trial and error is sometimes necessary and dry running the code would be a great feature to have in that regard.
Hmm this sounds interesting. I tried to hash up something quickly that could help with something like that. Please see http://www.jemajoign.org/code/dry_run.html. Try a few queries update/delete/insert queries on there. If this kind of an approach can help (i.e. offering a client-side feature to change a query to a dry-run query), I can clean up the code and put comments and stuff. Also I don't have much experience making parsers, so I doubt it's very robust.
This artifact has been marked as a duplicate of artifact 2521245 with reason:
This artifact has been marked as a duplicate of artifact 1410699 with reason:
sorry, used wrong bug number before...