| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
supports it.
|
| |
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
| |
Given the change to using `bigint` as type for auto-generated primary keys (as per https://github.com/rails/rails/pull/26266), I propose updating the Active Record Basics guide to explicitly state the type being used so as to avoid confusion as to the type of integer used, especially as the type can vary depending on the database used.
|
|
|
|
| |
[ci skip]
|
| |
|
|\
| |
| |
| |
| | |
saveriomiroddi/sav-correct_updated_at_guide_explanation
ActiveRecord Basics guide: correct explanation of the `updated_at` logic [ci skip]
|
| |
| |
| |
| |
| |
| | |
skip]
It's misleanding/incorrect to state that `updated_at` is set on updates, since creation != update (and the column is actually set on creation, too).
|
| |
| |
| |
| |
| | |
http links will be redirected to the https version, but still better to
just directly link to the https version.
|
|/
|
|
|
|
|
| |
[ci skip] A regular expression was used to find a lot of missing Oxford
commas and add them. The regular expression was as follows.
", ([a-zA-Z0-9.\`:'\"]+ ){1,6}(or|and) "
|
|
|
|
|
| |
* rDBMS -> RDBMS. There is only place using rDBMS.
* a SQL -> an SQL
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Update active_record_basics.md
I made a bit of clarification for people, who are not familiar with SQL (pretty much like me). However, I don't know what tutorial for MySQL is better, so I haven't inserted a link yet.
* [ci skip] For those who new to GitHub
Added more instructions for contributing guides. Without them, it was somewhat confusing for me to find what I should actually do.
* Update active_record_basics.md
Fixed grammar and text wrapping as requested.
* Update contributing_to_ruby_on_rails.md
Revised instructions.
* Update contributing_to_ruby_on_rails.md
Typos
* Update active_record_basics.md
* [ci skip] Update active_record_basics
Added a few links to SQL tutorials found on the net.
Also, changed MySQL to SQL (or one of its extensions) - I think that it's a good compromise.
* [ci skip] I think now it's more clear what to do.
* [ci skip] Fixed strings
[Rafael Mendonça França + loothunter1]
|
| |
|
|
|
|
| |
Guides [ci skip]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
- We no longer add `null: false` for timestamps columns as per
rails/rails@a939506.
- Followup of
https://github.com/rails/docrails/commit/14867b1a9af813b0147bba2ae06675137d61d77b.
|
|
|
|
|
|
|
| |
This reverts commit 96355e87cba247246234386b0af9273cc5d59db9, reversing
changes made to a00c36feea6c0271b5ad48a949ef294514fdef52.
See https://github.com/rails/rails/pull/23366#issuecomment-177714429
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to fill in some missing information as apart of #22931.
It's on purpose that the sample `Message` model inherits from
`ActiveRecord::Base` -- Active Record is not meant to be coupled to
Rails, and we can't guarantee that users outside of the Rails world will
have an `ApplicationRecord` class that inherits from
`ActiveRecord::Base`.
[ci skip]
|
|
|
|
| |
Still more to do. Please assist!
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's pretty common for folks to monkey patch `ActiveRecord::Base` to
work around an issue or introduce extra functionality. Instead of
shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can
hold all those custom work the apps may need.
Now, we don't wanna encourage all of the application models to inherit
from `ActiveRecord::Base`, but we can encourage all the models that do,
to inherit from `ApplicationRecord`.
Newly generated applications have `app/models/application_record.rb`
present by default. The model generators are smart enough to recognize
that newly generated models have to inherit from `ApplicationRecord`,
but only if it's present.
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Closes #21121
|
| |
|
| |
|
|
|
|
| |
- Also changed 'a' to 'an' for 'Article' word.
|
|
|
|
|
|
|
| |
getting_started.html#the-mvc-architecture is lost by this commit
2f06c94e38a116fdfa43d7b7117e6bf911a0bff5 (Mar 14 2012 !).
So replace it with wikipedia link.
|
| |
|
|\
| |
| | |
Changed `IN` to `ON` in markdown renderer condition
|
| |
| |
| |
| | |
- Changed `IN` to `ON` in all note sentences in guides.
|
|/ |
|
|
|
|
| |
References #18148.
|
| |
|
| |
|
|
|
| |
The current one is old-of-date and doesn't make the browser navigation to the correct heading.
|
|
|
|
| |
validation fails. [skip ci]
|
| |
|
| |
|
|
|
|
|
|
| |
Update a link to point to right section in api docs
Fix a typo
|
| |
|
|
|
| |
Change the plural of Deer word in the naming conventions
|
|
|
|
|
|
|
| |
Also, constantizing the default_fixture_model_name when it gets loaded
in from the file. Later, when the class_name is passed to a new
FixtureSet, a deprecation warning will occur if the class_name is a
string.
|
|
|
| |
First deprecated, now removed: https://github.com/rails/rails/commit/9add7608f1acaa68b025470e7a38901d7e6161ca#activerecord/lib/active_record/attribute_methods/primary_key.rb
|
| |
|