Updating change log and docs for Schema::drop.

taylorotwell · taylorotwell · commit bb506bb30bc7 · 2012-04-20T11:37:05.000-05:00
diff --git a/laravel/documentation/changes.md b/laravel/documentation/changes.md
@@ -53,6 +53,7 @@
 - Fixed bug present when using Eloquent models with Twig.
 - Allow multiple views to be registered for a single composer.
 - Added `Request::set_env` method.
+- `Schema::drop` now accepts `$connection` as second parameter.
 
 <a name="upgrade-3.2"></a>
 ## Upgrading From 3.1
diff --git a/laravel/documentation/database/schema.md b/laravel/documentation/database/schema.md
@@ -37,6 +37,10 @@ Let's go over this example. The **create** method tells the Schema builder that
 
 	Schema::drop('users');
 
+#### Dropping a table from a given database connection:
+
+	Schema::drop('users', 'connection_name');
+
 Sometimes you may need to specify the database connection on which the schema operation should be performed.
 
 #### Specifying the connection to run the operation on:
