RIPPON! doesn't re-write the database files after the user adds/changes an entry (ie. with the --artist=... options or the add_cd() sub). Of course, this isn't mentioned in the documentation, so the user will assume that the information they entered is going to be preserved, and will be pretty P.O.'ed when they discover that all that hard work has gone to waste. Maybe this should be a `dangerous' bug?