| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
[ci skip]
This was pointed out on
https://github.com/rails/rails/issues/15583#issuecomment-239212831
The comment was lost in the changes made by
fcd0ac066e0959a9f4fa4459a27e041abe8eb52a and
3e1373a773085d5f19cb6a466ab2736cc1ca2713
|
| |
|
|
|
|
|
|
| |
In #23179 the migration generator was changed to no longer output `index: true` for `references` migrations. This updates the migrations guide to remove `index: true` from relevant examples.
[ci skip]
|
| |
|
|\
| |
| |
| | |
Add support for specifying comments for tables, columns, and indexes in database itself
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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]
|
| |
| |
| |
| |
| |
| | |
- 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.
|
|/ |
|
|\
| |
| |
| |
| | |
Conflicts:
guides/source/association_basics.md
|
| |
| |
| |
| |
| |
| |
| | |
- We no longer add `null: false` for timestamps columns as per
rails/rails@a939506.
- Followup of
https://github.com/rails/docrails/commit/14867b1a9af813b0147bba2ae06675137d61d77b.
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
|
|
| |
Fixed errors in rails migrations docs [ci skip]
Fixed errors in rails security docs [ci skip]
|
|
|
| |
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 …`
|
|
|
|
| |
Still more to do. Please assist!
|
|
|
|
|
| |
Even though this means more things to change when we bump after a
release, it's more important that our examples are directly copyable.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
option for column
|
|
|
| |
Add 'db/'; corrects structure.rb to structure.sql
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
| |
In rails generally migration file's timestamp is "YYYYMMDDHHMMSS".
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
this behavior was changed in b8e1f202676b4788c56241b124c401beff9f4014
|
|
|
|
|
|
| |
* insert 'and' into a poorly formed sentence.
* avoid using 'reverse' twice in the same sentence (which would indicate
the opposite of what is meant)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- Changed `IN` to `ON` in all note sentences in guides.
|
|
|
|
| |
References #18148.
|
| |
|
|
|
|
|
|
| |
Related to this PR #16062
[ci skip]
|
|
|
| |
[skip ci]
|
|
|
|
|
|
|
| |
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]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
This will need to setup permanent redirect for the old guide.
|