Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
Y
yii2
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
PSDI Army
yii2
Commits
b09d0f12
Commit
b09d0f12
authored
Apr 29, 2014
by
Paul K
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
overwrite -> override
parent
6f7be5ee
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
4 additions
and
4 deletions
+4
-4
intro-upgrade-from-v1.md
docs/guide/intro-upgrade-from-v1.md
+1
-1
Migration.php
framework/db/Migration.php
+3
-3
No files found.
docs/guide/intro-upgrade-from-v1.md
View file @
b09d0f12
...
...
@@ -181,7 +181,7 @@ In the above, two scenarios are declared: `backend` and `frontend`. For the `bac
The
[
[yii\base\Model::rules()|rules()
]
] method is still used to declare validation rules. Note that because
of the introduction of
[
[yii\base\Model::scenarios()|scenarios()
]
], there is no more
`unsafe`
validator.
In most cases, you do not need to over
writ
e
[
[yii\base\Model::scenarios()|scenarios()
]
]
In most cases, you do not need to over
rid
e
[
[yii\base\Model::scenarios()|scenarios()
]
]
if the
[
[yii\base\Model::rules()|rules()
]
] method fully specifies the scenarios and there is no need to declare
`unsafe`
attributes.
...
...
framework/db/Migration.php
View file @
b09d0f12
...
...
@@ -17,11 +17,11 @@ use yii\di\Instance;
* Each child class of Migration represents an individual database migration which
* is identified by the child class name.
*
* Within each migration, the [[up()]] method should be over
writt
en to contain the logic
* Within each migration, the [[up()]] method should be over
ridd
en to contain the logic
* for "upgrading" the database; while the [[down()]] method for the "downgrading"
* logic. The "yii migrate" command manages all available migrations in an application.
*
* If the database supports transactions, you may also over
writ
e [[safeUp()]] and
* If the database supports transactions, you may also over
rid
e [[safeUp()]] and
* [[safeDown()]] so that if anything wrong happens during the upgrading or downgrading,
* the whole migration can be reverted in a whole.
*
...
...
@@ -55,7 +55,7 @@ class Migration extends \yii\base\Component
/**
* This method contains the logic to be executed when applying this migration.
* Child classes may over
writ
e this method to provide actual migration logic.
* Child classes may over
rid
e this method to provide actual migration logic.
* @return boolean return a false value to indicate the migration fails
* and should not proceed further. All other return values mean the migration succeeds.
*/
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment