title: Laravel Schema builder drop table on specific connection
body: <p>I created a <code>users</code> table using Laravel's schema builder. Here is the migration:</p>
  
  <pre><code>class CreateUsersTable extends Migration {
  
          /**
           * Run the migrations.
           *
           * @return void
           */
          public function up()
          {
                  Schema::connection('mysql-internal')-&gt;create('users', function(Blueprint $table)
                  {
                          $table-&gt;increments('id');
                          $table-&gt;string('username');
                          $table-&gt;string('password');
                          $table-&gt;timestamps();
                  });
          }
  
          /**
           * Reverse the migrations.
           *
           * @return void
           */
          public function down()
          {
                  Schema::connection('mysql-internal')-&gt;drop('users');
          }
  
  }
  </code></pre>
  
  <p>After running this migration, I then rolled it back using <code>php artisan migrate:rollback</code>. However, it looks like <code>down</code> method did not respect my <code>connection</code>. The <code>users</code> table was dropped from my default mysql database rather than the <code>mysql-internal</code> that I specified.</p>
  
  <p>Did I do something wrong here? I am using Laravel 4.2.17.</p>