<p>I created a Rails application normally. Then created the scaffold for an event class. Then tried the following code. When run it complains about a InvalidAuthenticityToken when the destroy method is executed. How do I authenticate to avoid this response?</p>

<pre><code>require 'rubygems'
require 'activeresource'

class Event &lt; ActiveResource::Base
  self.site = "http://localhost:3000"
end

e = Event.create(
  :name =&gt; "Shortest Event Ever!",
  :starts_at =&gt; 1.second.ago,
  :capacity =&gt; 25,
  :price =&gt; 10.00)

e.destroy
</code></pre>

By default, all innodb databases in a given mysql server installation use the same physical pool of data files, so conceivably "drop database A"  could affect database B.  Since "drop database" is likely to involve heavy reorgainsing of the innodb data files, it's conceivable that it's a blocking operation, either because of the intensity of the operation, or by design.
However, I think you can make each database use different physical files, although I haven't tried that myself, so you'll have to figure out the specifics for yourself. Failing that, then you may need to use two different mysql installs side-by-side on the same machine, which is perfectly doable.