Using phpMyAdmin (NewsForge)
So many open source projects depend on MySQL that it's almost impossible for administrators and other open source enthusiasts to avoid working with at least one MySQL database. MySQL's command line interface is easy enough to use, but if you don't feel like reaching for a five-pound MySQL reference book or Googling for proper SQL syntax, phpMyAdmin is a great alternative to learning MySQL commands by heart."
Posted Aug 11, 2006 0:55 UTC (Fri)
by sholdowa (guest, #34811)
[Link] (6 responses)
Anything that's accessed by more than one person (ie the three fingered salute approach to management is not appropriate) needs to be managed by someone who knows what they're talking about.
If you want to play with databases then go out and learn how to do it properly. If your job requires it, then get the company to pay for the course. That way you won't accidentally drop your database (:
Posted Aug 11, 2006 4:51 UTC (Fri)
by h2 (guest, #27965)
[Link]
Posted Aug 11, 2006 7:53 UTC (Fri)
by HappyCamp (guest, #29230)
[Link] (1 responses)
Personally I like having phpMyAdmin. Makes my job easier in setting up software when I rarely have to use SQL commands in the first place it is quite useful.
Also I don't think the security issues are that much since you can mitigate them pretty easily. Put it in a non-standard location, also only allow access to it from certain IP addresses, and you can set Apache to only allow access to it via SSL and Apache passwords.
Posted Aug 11, 2006 8:37 UTC (Fri)
by cate (subscriber, #1359)
[Link]
Posted Aug 11, 2006 8:17 UTC (Fri)
by flewellyn (subscriber, #5047)
[Link]
Posted Aug 11, 2006 12:01 UTC (Fri)
by Dom2 (guest, #458)
[Link]
Posted Aug 11, 2006 16:00 UTC (Fri)
by georgm (subscriber, #19574)
[Link]
(btw - I use postgresql, but from time to time I need to do something with mysql)
For queries and other SQL stuff I prefer the command line
Sorry, I completely disagree with this. If you don't understand SQL, then you've no right to be in a place you need to do so. If you're using a project that uses it for storage, then it, not you should be monkeying in the database.Using phpMyAdmin (NewsForge)
I agree. Not to mention that adding one more layer of insecurity doesn't do anyone any good either. I see every week new phpmyadmin exploits being targetted in my 404 logs. And all just to avoid learning a few simple commands, which you cut and paste into your script after the first time you make them.Using phpMyAdmin (NewsForge)
I completely disagree with you disagreeing with the article :)Using phpMyAdmin (NewsForge)
I disagree to the comment too.Using phpMyAdmin (NewsForge)
If managing mysql is not a daily job, I think it is more secure to use a graphical interface: less probable to do things wrong (and maybe without noticing it). It really depend on usage. personally I use console for replication jobs but phpmyadmin for (rare) permit managing, check permisions and debugging web scripts.
Well, I understand SQL just fine, and I still find phpPGAdmin (the PostgreSQL version of Using phpMyAdmin (NewsForge)
phpMyAdmin) useful for some basic things. I can type out every single command to add a
column or a constraint, but that doesn't mean I want to.
Hmmm. I know SQL very well -- PostgreSQL. On the rare occasions that I need to go near the Using phpMyAdmin (NewsForge)
vile MySQL thing, I find that phpmyadmin makes it much easier than trying to remember the
particulars of its SQL syntax.
I like such tools not for querying, but for administrative tasks.Using phpMyAdmin (NewsForge)
For adding a user, setting permissions etc. I prefer a tool over the command line version.
But maybe it is a good idea for mysql and their not-so-SQLish syntax ;)