Browse Source

Updating change log and docs for Schema::drop.

Taylor Otwell 12 years ago
parent
commit
bb506bb30b
2 changed files with 5 additions and 0 deletions
  1. 1 0
      laravel/documentation/changes.md
  2. 4 0
      laravel/documentation/database/schema.md

+ 1 - 0
laravel/documentation/changes.md

@@ -53,6 +53,7 @@
 - Fixed bug present when using Eloquent models with Twig.
 - Fixed bug present when using Eloquent models with Twig.
 - Allow multiple views to be registered for a single composer.
 - Allow multiple views to be registered for a single composer.
 - Added `Request::set_env` method.
 - Added `Request::set_env` method.
+- `Schema::drop` now accepts `$connection` as second parameter.
 
 
 <a name="upgrade-3.2"></a>
 <a name="upgrade-3.2"></a>
 ## Upgrading From 3.1
 ## Upgrading From 3.1

+ 4 - 0
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');
 	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.
 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:
 #### Specifying the connection to run the operation on: