From bb506bb30bc701095a33a7b1e35b0f5616fd9641 Mon Sep 17 00:00:00 2001 From: Taylor Otwell Date: Fri, 20 Apr 2012 11:37:05 -0500 Subject: [PATCH] Updating change log and docs for Schema::drop. --- laravel/documentation/changes.md | 1 + laravel/documentation/database/schema.md | 4 ++++ 2 files changed, 5 insertions(+) diff --git a/laravel/documentation/changes.md b/laravel/documentation/changes.md index 21b07ef1..169fe0ac 100644 --- a/laravel/documentation/changes.md +++ b/laravel/documentation/changes.md @@ -53,6 +53,7 @@ ## Laravel 3.2 - 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. ## Upgrading From 3.1 diff --git a/laravel/documentation/database/schema.md b/laravel/documentation/database/schema.md index ed55d84e..16ed318c 100644 --- a/laravel/documentation/database/schema.md +++ b/laravel/documentation/database/schema.md @@ -37,6 +37,10 @@ #### Dropping a table from the database: 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: