Annajwaszahro
/
MIF_E31222691
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updating change log and docs for Schema::drop.

This commit is contained in:
Taylor Otwell 2012-04-20 11:37:05 -05:00
parent a92ab1ca30
commit bb506bb30b
2 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
laravel/documentation/changes.md
View File

@ -53,6 +53,7 @@ ## Laravel 3.2
- 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
laravel/documentation/database/schema.md
View File

@ -37,6 +37,10 @@ #### Dropping a table from the database:
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: