openstack/barbican
Code Issues Proposed changes

Remove duplicate words in documentation

Browse Source 
Remove duplicate words in developer's document 'Database Migrations'.

Change-Id: I04d6fc46b5482ab4d1637552bd8686f3bb9911fd
This commit is contained in:
Hironori Shiina 2015-10-09 10:23:46 +00:00
parent 201861fd2d
commit b1b5b07434
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/contribute/database_migrations.rst
View File

@ -34,7 +34,7 @@ To achieve this goal, the following rules will be observed for schema changes:
a. Create a version of the application not dependent on the removed
column/table
b. Replace all nodes with this new application version
c. Create an Alembic version file to remove remove the column/table
c. Create an Alembic version file to remove the column/table
d. Apply this change in production manually, or automatically with a future
version of the application
@ -122,7 +122,7 @@ instructions).
`server_default='0'` for False, or `server_default='1'` for True. For
DateTime attributes, use `server_default=str(timeutils.utcnow())` to
default to the current time.
2. If you add `any` constraint, please always `always` name them in the
2. If you add `any` constraint, please `always` name them in the
barbican.model.models.py module, and also in the Alembic version
modules when creating/dropping constraints, otherwise MySQL migrations
might crash.