Did I tell you about Sequel Pro?
You can use it to connect to your local MAMP and also to remote LAMP mysql servers (via SSH). Why is this so awesome?
Well, not only is it 100 times faster than that phpMyAdmin, but you can edit your DB super easily, like a spreadsheet. It is a snap to filter/search/order a table for viewing and editing.
Caveat emptor: what I am about to show you can do tremendous damage. You can accidentally kill your entire application, so BACK YOUR DATABASES UP! Test on a copy first.
You can do simple things like turn 1′s to 0′s and quickly disable a drupal module faster than drush can (but watch out if you don’t know your dependencies).
I had this interesting and daunting problem:
I am working on this site for a soccer league that has a couple hundred teams and I realize that I need to modify a whole slew of node titles based on values that appear in their CCK fields.
Many of the Organic Group Group nodes (each team is a group)
Views Bulk Operations gets me part, but not all the way quickly enough for this one-time operation.
I’m not crafty enough to write a join and update statement across all these tables, but I do already have a view listing Teams and CCK fields for Division and Type.
Hey, if I scroll down to the bottom of the view, I can copy the query right from views into Sequel Pro!
Holy Moly. It just works. As it should.
Now I can just go down the list and edit my node titles.
Because there was a pattern here, I ended up using the fabulous auto nodetitle module and tokens. I temporarliy added a pattern to the node titles of my team content type and used views bulk operations to update some of my node titles. After the update, i set the pattern to be used only if the title was blank.
Even though I solved my use case another way, I can see plenty of use for this technique in the future. Great way to fix typos in content, for example.