MySQL Sandbox and laziness

Laziness strikes again. MySQL Sandbox was created with the intent of avoiding repetitive work when creating and using several servers. Turns out that even the current framework, which many say that is really time saving and enhances productivity, was not enough. So my desire for laziness, which is, as everybody should know a chief virtue for a programmer has made me code a shortcut script, which can joggle sandboxes as never before.

Enter the sb script (available in version 3.0.03). Now I can shorten my typing experience with sandboxes quite a lot:

  $ sb 5135
  # same as calling 
  # $SANDBOX_HOME/msb_5_1_35/use

Nice, isn't it? It saves me quite a lot of keys. Not only that. If this sandbox is not active, the script will start it for me. That's yet a few keystrokes more that I am saving.
What if I want a replication sandbox? Easy:

  $ sb r5135
  # same as calling 
  # $SANDBOX_HOME/rsandbox_5_1_35/m

For a multiple sandbox instead of a replication one, use "m5135."
Now, for the really amazing stuff. Let's suppose that the sandbox doesn't exist yet.
No problem.

  $ sb 5.1.35
  # same as calling 
  # make_sandbox 5.1.35
  # and
  # $SANDBOX_HOME/msb_5_1_35/use

And if you don't have a pre-expanded directory for 5.1.35 under $SANDBOX_BINARY as I do? Also this is easily done:

  $ sb mysql-5.1.35-YOUR_OS.tar.gz
  # same as calling 
  # make_sandbox mysql-5.1.35-YOUR_OS.tar.gz
  # and
  # $SANDBOX_HOME/msb_5_1_35/use

Creating and using a replication sandbox is really easy as well:

  $ sb r5.1.35
  # same as calling 
  # make_replication_sandbox 5.1.35
  # and
  # $SANDBOX_HOME/rsandbox_5_1_35/m

The manual explains the above cases and some more (Yes: there is actually more).
Go on! get lazy!