| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
PR #18772 changed the parameters of `stale?` to use `kwargs`.
[As for this comment](https://github.com/rails/rails/pull/18872/files#r24456288)
the default value for the `etag` parameter should be `record`, not `nil`.
This commit fixes the code and introduces a test that:
- passed before #18872
- fails on the current master (after #18772)
- passes again after setting the default value of `etag` to `record`.
|
|\
| |
| | |
Convert stale? and fresh_when to use keyword arguments.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Like for real this time. I checked.
|
|\ \
| | |
| | | |
Fixed typos in ActiveRecord CHANGELOG [ci skip]
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add an option `end` to `find_in_batches`
|
| | | |
| | | |
| | | |
| | | | |
that complements the `start`parameter to specify where to stop batch processing
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The various databases don't actually need significantly different
handling for this behavior, and they can achieve it without knowing
about the type of the object.
The old implementation was returning a string, which will cause problems
such as breaking TZ aware attributes, and making it impossible for the
adapters to supply their logic for time objects.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
alex-handley/enhancement/dependent_documentation_fix
Documentation Fix: Corrects explanation of what happens when dependent is not set
|
| | | |
| | | |
| | | |
| | | |
| | | | |
By default the foreign key will remain set with the parent id after
destroy is fired.
|
| | | |
| | | |
| | | |
| | | | |
Fixes #18871
|
|\ \ \ \
| |_|_|/
|/| | | |
Document lazy lookup behavior for controllers [ci skip]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Pull request #7082 added lazy lookup to controllers using the translate
method, but the documentation still stated that it was available for
views only.
[ci skip]
|
| | | |
| | | |
| | | |
| | | | |
Significantly faster than `SimpleDelegator`.
|
|\ \ \ \
| | | | |
| | | | | |
Remove warning from ActionView::Helpers::Tags::Translator
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
This removes the following warning:
/GitHub/rails/actionview/lib/action_view/helpers/tags/translator.rb:19: warning: private attribute?
|
|\ \ \ \
| |_|_|/
|/| | | |
An array type is a part of `sql_type`
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`sql_type` is reused in `lookup_cast_type`. If making it a part of
`sql_type` when handled array option first, it isn't necessary to do
again.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The default of the global might change. It's better to reset it to
what it was than a hardcoded value.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
yuki24/remove-warning-from-generators-named-base-test
Remove warning from generator named base test
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This removes the following warning:
railties/test/generators/named_base_test.rb:9: warning: method redefined; discarding old pluralize_table_names
activesupport/lib/active_support/core_ext/class/attribute.rb:86: warning: previous definition of pluralize_table_names was here
railties/test/generators/named_base_test.rb:9: warning: method redefined; discarding old pluralize_table_names=
activesupport/lib/active_support/core_ext/class/attribute.rb:83: warning: previous definition of pluralize_table_names= was here
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Remove warning from Plugin Generator
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
This removes the following warning:
rails/railties/lib/rails/generators/rails/plugin/plugin_generator.rb:321: warning: shadowing outer local variable - content
|
|\ \ \ \
| |/ / /
|/| | | |
Explicitly ignored wildcard verbs from head_routes
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
In match_head_routes, deleted the routes in which request.request_method was empty (matches all HTTP verbs) when responding to a HEAD request. This prevents catch-all routes (such as Racks) from intercepting the HEAD request.
Fixes #18698
|
| | | |
|
| | |
| | |
| | |
| | | |
Added by 101c19f55f5f1d86d35574b805278f11e9a1a48e.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
kamipo/fix_rounding_problem_for_postgresql_timestamp_column
Fix rounding problem for PostgreSQL timestamp column
|
|/ / /
| | |
| | |
| | |
| | | |
If timestamp column have the precision, it need to format according to
the precision of timestamp column.
|
|\ \ \
| | | |
| | | | |
Respect the database default charset for `schema_migrations` table.
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
The charset of `version` column in `schema_migrations` table is depend
on the database default charset and collation rather than the encoding
of the connection.
|
|\ \ \
| | | |
| | | | |
Add `auto_increment?` instead of `extra == 'auto_increment'`
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Remove unused line
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Missing `@` [ci skip]
|
|/ / |
|
| |
| |
| |
| |
| | |
This predicate is only used in `query_attribute`, and is relatively easy
to remove without adding a bunch of is a checks.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This predicate was only to figure out if it's safe to do case
insensitive comparison, which is only a problem on PG. Turns out, PG can
just tell us whether we are able to do it or not. If the query turns out
to be a problem, let's just replace that method with checking the SQL
type for `text` or `character`. I'd rather not burden the type objects
with adapter specific knowledge.
The *real* solution, is to deprecate this behavior entirely. The only
reason we need it is because the `:case_sensitive` option for
`validates_uniqueness_of` is documented as "this option is ignored for
non-strings". It makes no sense for us to do that. If the type can't be
compared in a case insensitive way, the user shouldn't tell us to do
case insensitive comparison.
|
| |
| |
| |
| |
| |
| |
| | |
The type code is actually quite accessible, and I'm planning to
encourage people to look at the files in the `type` folder to learn more
about how it works. This will help reduce the noise from code that is
less about type casting, and more about random AR nonsense.
|
| |
| |
| |
| |
| |
| |
| | |
It only existed to make sure the subclasses of `Delegator` were YAML
serializable. As of Ruby 2.2, these are YAML dumpable by default, as it
includes
https://github.com/tenderlove/psych/commit/2a4d9568f7d5d19c00231cf48eb855cc45ec3394
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows us to remove `Type::Value#klass`, as it was only used for
multi-parameter assignment to reach into the types internals. The
relevant type objects now accept a hash in addition to their previous
accepted arguments to `type_cast_from_user`. This required minor
modifications to the tests, since previously they were relying on the
fact that mulit-parameter assignement was reaching into the internals of
time zone aware attributes. In reaility, changing those properties at
runtime wouldn't change the accessor methods for all other forms of
assignment.
|
|\ \
| | |
| | | |
NameError#missing_name? can just use NameError#name if the arg is a Symbol
|
| | |
| | |
| | |
| | |
| | |
| | | |
NameError#name returns a missing name as a symbol, so if the given name
is a symbol, it doesn't have to use #missing_name to get the last constant
name in the error message.
|
|\ \ \
| | | |
| | | | |
remove noise from AM tests
|
| |/ / |
|
|\ \ \
| |/ /
|/| | |
Use the Rails favicon.ico instead of the ruby favicon.ico for rails guides [ci skip]
|