101–110 of 112 posts
Earlier quoted context omitted.
Or learn how to use the CLI client to connect. No need to install a awkward wrapper software layer.
You seem to be a software developer who is advocating that people not automate something that's tedious (writing and running SELECT and UPDATE queries). Weird.
Earlier quoted context omitted.
You seem to be a software developer who is advocating that people not automate something that's tedious (writing and running SELECT and UPDATE queries). Weird.
You can automate with scripts. No need to use a fancy GUI for this.
With a GUI, you can click 3 times and browse 3 tables. That's just not possible without a GUI.
If GUIs didn't save people (lots of) time, no one would have invented them and the software industry would be moving away from them.
Besides being way faster and more efficient, GUIs do things that CLIs don't:
- linting/error-checking/autocomplete for SQL
- checking query sanity (warn before an unconstrained DELETE for example)
- copy/paste data (within the database and between applications)
- jump from FK cell to the row it references
The list goes on.
I encourage people to google how to run phpMyAdmin, MySQL Workbench, or Sequel Pro locally, and use port forwarding over SSH. It's super simple. Here is a command that forwards all traffic to localhost:3306 across the ssh tunnel to example.com:3306 (the mysql default port). ssh user@example.com -L 3306:localhost:3306 I would never run a DB admin application on the live server because it's just one more piece that mig…
Earlier quoted context omitted.
You can automate with scripts. No need to use a fancy GUI for this.
And what if I don't want to write scripts because other people have already automated all common database browsing/editing tasks for me? What if I don't want to reinvent the wheel? With a GUI, you can click 3 times and browse 3 tables. That's just not possible without a GUI. If GUIs didn't save people (lots of) time, no one would have invented them and the software industry would be moving away from them. Besides bei…
- they can be stored in a version control system
- your coworkers can run them at their dev environment
- they can be used for automatic deployment
- you can test it in a dev environment before running at a production server. With GUI tools you have to remember and repeat exact steps you did before
- You can review the script or ask someone to look at it
I think GUI tools might be good for browsing and exploring database but not for making changes.
Earlier quoted context omitted.
MySQL Workbench works fine though?
Last time I tried it (about two years ago). It would crash all the time on Ubuntu. Went back to PHPMyAdmin.
Earlier quoted context omitted.
Apart from security, are there any other benefits?
Sequel Pro (free open source, despite name) is a native application which is much nicer to use than phpMyAdmin. So, yes there's benefits other than security.
Earlier quoted context omitted.
Yes it is. It is a bug, that may be exploitable. There's no contradiction there.
Global variables are not bugs -- at worse they are bad style and can cause bugs. As for your other comments, there's this "burden of proof" thing.
Earlier quoted context omitted.
Or learn how to use the CLI client to connect. No need to install a awkward wrapper software layer.
You seem to be a software developer who is advocating that people not automate something that's tedious (writing and running SELECT and UPDATE queries). Weird.
Tedium in a GUI is still tedium.
https://twitter.com/totally_unknown/status/74275332346864026...
repetition of "completing" in first line.