aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_migrations.md
Commit message (Collapse)AuthorAgeFilesLines
* Fix wording related to adapters supporting database comments [ci skip]Prathamesh Sonpatki2016-04-181-2/+2
|
* Merge pull request #22911 from Envek/database_commentsJeremy Daer2016-04-161-0/+8
|\ | | | | | | Add support for specifying comments for tables, columns, and indexes in database itself
| * Add support for specifying comments for tables, columns, and indexes.Andrey Novikov2016-04-161-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | Comments are specified in migrations, stored in database itself (in its schema), and dumped into db/schema.rb file. This allows to generate good documentation and explain columns and tables' purpose to everyone from new developers to database administrators. For PostgreSQL and MySQL only. SQLite does not support comments at the moment. See docs for PostgreSQL: http://www.postgresql.org/docs/current/static/sql-comment.html See docs for MySQL: http://dev.mysql.com/doc/refman/5.7/en/create-table.html
* | documentation for add_references index option [ci skip]Vipul A M2016-04-171-1/+2
|\ \ | |/ |/| documentation for add_references index option [ci skip]
| * [ci skip] docs for add_references index optionAlex Handley2016-04-161-1/+2
| | | | | | | | | | | | - Add link for finding the addional options for index. - Add example for unique index as this is a common requirement. - Add link in guide for index options.
* | MariaDB Documentationiangilfillan2016-04-141-2/+2
|/
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2016-03-061-2/+2
|\ | | | | | | | | Conflicts: guides/source/association_basics.md
| * [ci skip] Update all guides with `null: false` change in migrationsPrathamesh Sonpatki2016-03-031-3/+3
| | | | | | | | | | | | | | - We no longer add `null: false` for timestamps columns as per rails/rails@a939506. - Followup of https://github.com/rails/docrails/commit/14867b1a9af813b0147bba2ae06675137d61d77b.
* | Changed behaviour of timestamps helper by create_table migration generator ↵Mehmet Emin İNAÇ2016-03-031-1/+1
| | | | | | | | [ci skip]
* | Fixed grammatical errors in rails docs [ci skip]Matt Michnal2016-02-091-2/+2
|/ | | | | | Fixed errors in rails migrations docs [ci skip] Fixed errors in rails security docs [ci skip]
* use bin/rails default instead of rake commands [ci skip]Gaurav Sharma2016-01-191-7/+7
| | | I go through the `http://edgeguides.rubyonrails.org/` and found `rake` commands in various files that are in RAILS 5.0 implement by `bin/rails` command. I try to change all that can be directly use `bin/rails …`
* Refer to rails command instead of rake in a bunch of placesDavid Heinemeier Hansson2015-12-181-15/+15
| | | | Still more to do. Please assist!
* Use a real migration version number in docsMatthew Draper2015-12-151-19/+19
| | | | | Even though this means more things to change when we bump after a release, it's more important that our examples are directly copyable.
* Use a deliberately-invalid migration version in all doc examplesMatthew Draper2015-12-151-19/+19
| | | | | | | | | | If we use a real version, at best that'll be an onerous update required for each release; at worst, it will encourage users to write new migrations against an older version than they're using. The other option would be to leave these bare, without any version specifier. But as that's just a variant spelling of "4.2", it would seem to raise the same concerns as above.
* Issue #22139 : Edge Guides - ActiveRecord Migrations - Remove required ↵atul-shimpi2015-11-011-2/+0
| | | | option for column
* Update active_record_migrations.mdAnna Ershova2015-10-151-1/+1
| | | Add 'db/'; corrects structure.rb to structure.sql
* Clarifies db can be set up from structure.sql alsoAnnaErshova2015-10-151-1/+1
| | | | | | | | I added that *structure.sql* file can be used when *db:reset* is run. *db:reset* tasks states *db:reset* loads database from *db/schema.rb* or *db/structure.sql* depending on the configuration (although *db/schema.rb* is the default), hence the change.
* [ci skip] Update what methods `Migration#change` can reverseyui-knk2015-08-311-14/+21
| | | | | | | | | | * Documentations and comments about what methods `Migration#change` can reverse is out of date. For example `change_column_default` is now reversible by this [commit](https://github.com/rails/rails/pull/20018). * Comments about `CommandRecorder` dose not match with Rails Guide. For example `add_foreign_key` is listed only on Rails Guide.
* [ci skip] Fix migration file's timestampyui-knk2015-08-241-1/+1
| | | | In rails generally migration file's timestamp is "YYYYMMDDHHMMSS".
* [ci skip] Give in-depth explanation of migrations vs. seeds.rbBrooks Reese2015-08-081-4/+9
|
* [ci skip] migration and association guides: added some remarks about join tablesr11runner2015-08-041-10/+8
|
* fix pluralization in doc [ci skip]Jordon Dornbos2015-06-291-1/+1
|
* Update guide for new change_column_default syntaxPrem Sichanugrist2015-06-261-6/+8
|
* fix doc about foreign key name [ci skip]yuuji.yaginuma2015-06-121-1/+2
| | | | this behavior was changed in b8e1f202676b4788c56241b124c401beff9f4014
* [ci skip] Improve phrasing in AR migrations docs.Tim Wade2015-05-131-2/+2
| | | | | | * insert 'and' into a poorly formed sentence. * avoid using 'reverse' twice in the same sentence (which would indicate the opposite of what is meant)
* [ci skip] fix guides example on arbitrary SQL executionKonstantinos Rousis2015-04-011-1/+1
|
* Documenting remove_column as a reversible migration method [ci skip]Andrey Nering2015-03-251-0/+8
|
* Change 'a' to 'an' for 'HABTM' word [ci skip]Santosh Wadghule2015-03-231-1/+1
|
* [ci skip] Change `the null` to `a not null constraint`yui-knk2015-03-221-1/+1
|
* add foreign_key option to result of references column type [ci skip]yuuji.yaginuma2015-03-191-1/+1
|
* Improvements about schema dumping [ci skip]Andrey Nering2015-01-291-5/+10
|
* - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
| | | | - Changed `IN` to `ON` in all note sentences in guides.
* warn about reading guides in GitHubXavier Noria2014-12-231-0/+2
| | | | References #18148.
* Add `null` option to timestamps as migration generator does [ci skip]Zachary Scott2014-12-141-3/+3
|
* Add guides for `required` model generator option.Carlos Souza2014-12-091-0/+2
| | | | | | Related to this PR #16062 [ci skip]
* AR Migrations Guide#Foreign Keys: fix wrong tableJon Atack2014-10-241-1/+1
| | | [skip ci]
* Tiny follow-up to 1a69112Robin Dupret2014-06-271-3/+7
| | | | | | | Wrap list items to 80 chars and avoid relying on NOTE inside an item since they are meant to be parsed in paragraphs, not lists. [ci skip]
* fk: add docsYves Senn2014-06-261-58/+71
|
* :nail_care: wrap the tip from #15624 at 80 chars [ci skip]Zachary Scott2014-06-201-1/+2
|
* [ci skip] Add Tip for change_column_null and change_column_default in guidesAditya Kapoor2014-06-211-0/+2
|
* docs, refactor docs about column modifiers. [ci skip] [Matthew Draper & Yves ↵Yves Senn2014-06-101-12/+20
| | | | | | | | | | | | | | | | | | | | Senn] This is a follow up to #15602 which rendered the guides in a weird state: > You can also specify some options just after the field type between curly braces. You can use the following modifiers: > `null` Allows or disallows `NULL` values in the column. > NOTE: `null` and `default` cannot be specified via command line. The modifiers are now moved into a separate section. The generator simply referes to that section. Related to #15583. /cc @JuanitoFatas
* [ci skip] Rename: Rails Database Migration to Active Record Migration.Juanito Fatas2014-06-101-0/+988
This will need to setup permanent redirect for the old guide.