| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Was left in adfab2dcf4003ca564d78d4425566dd2d9cd8b4f
|
| |
|
|
|
|
|
|
|
| |
See #9683 for the reasons we switched to `distinct`.
Here is the discussion that triggered the actual deprecation #20198.
`uniq`, `uniq!` and `uniq_value` are still around.
They will be removed in the next minor release after Rails 5.
|
| | |
|
| | |
|
| |
|
| |
For Inline formats, changed ` (single backticks) to <tt> tag at active record rdoc as single backticks (`) don't work with rdoc. for inline format.
|
| |\
| |
| | |
typo fix [ci skip]
|
| | | |
|
| |\ \
| | |
| | | |
Fix NetAddr link [ci skip]
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| | |
we should ask the reflection for its name rather than storing the
reflection name in two places (an array and a reflection object)
|
| | | |
|
| | |
| |
| |
| |
| | |
This line introduced by the commit fd398475 for using
`Arel::Visitors::BindVisitor`. Currently it is not used.
|
| |\ \
| | |
| | | |
Avoid the heredoc in one line queries and simple queries
|
| | |/
| |
| |
| | |
Related with #20028.
|
| |/ |
|
| |\
| |
| | |
Add schema cache to new connection pool after fork
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Active Record detects when the process has forked and automatically
creates a new connection pool to avoid sharing file descriptors.
If the existing connection pool had a schema cache associated with it,
the new pool should copy it to avoid unnecessarily querying the database
for its schema.
The code to detect that the process has forked is in ConnectionHandler,
but the existing test for it was in the ConnectionManagement test file.
I moved it to the right place while I was writing the new test for this
change.
|
| |\ \
| | |
| | | |
Refactoring `ActiveRecord::Type::Integer` limit
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
Divide methods for handling column options separately
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | | |
Fix `serial?` with quoted sequence name
|
| | |/ / |
|
| |\ \ \
| | | |
| | | | |
docs for updating nested attributes while creating parent record
|
| | | | |
| | | |
| | | |
| | | | |
skip]
|
| | |_|/
|/| |
| | |
| | |
| | | |
We must account for receiving one less call to #new_connection, but the
test otherwise remains valid.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| | |
This patch
- reduces the duplication among the `reference`-family methods.
- better explains all the optians available for `add_reference`.
- redirects to user from `references` to `add_reference`.
Originated by #20184.
|
| | | |
|
| |\ \
| | |
| | | |
Reducing AR::ConPool's critical (synchronized) section
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Renamed `@reserved_connections` -> `@thread_cached_conns`. New name
clearly conveys the purpose of the cache, which is to speed-up
`#connection` method.
The new `@thread_cached_conns` now also uses `Thread` objects as keys
(instead of previously `Thread.current.object_id`).
Since there is no longer any synchronization around
`@thread_cached_conns`, `disconnect!` and `clear_reloadable_connections!`
methods now pre-emptively obtain ownership (via `checkout`) of all
existing connections, before modifying internal data structures.
A private method `release` has been renamed `thread_conn_uncache` to
clear-up its purpose.
Fixed some brittle `thread.status == "sleep"` tests (threads can go
into sleep even without locks).
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Move post checkout connection verification out of mutex.synchronize.
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
[ci skip] Remove comments about Rails 3.1
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Stems from https://github.com/rails/rails/pull/20105#issuecomment-100900939
where @senny said:
> From my point of view, all the docs (guides, API) are version bound.
> They should describe that version and continue to be available when newer versions are released.
> The cross referencing can be done by the interested user.
|
| |\ \ \
| | | |
| | | | |
remove redundant parenthesis
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Remove call to sanitize_sql_hash_for_conditions
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
This method has already been removed.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This can resolve confusing situation when a top level constant exists
but a namespaced version is identified.
Related to #19531.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
https://github.com/agrobbin/rails into agrobbin-sti-subclass-from-attributes
Conflicts:
activerecord/CHANGELOG.md
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If your STI class looks like this:
```ruby
class Company < ActiveRecord::Base
self.store_full_sti_class = false
class GoodCo < Company
end
class BadCo < Company
end
end
```
The expectation (which is valid) is that the `type` in the database is saved as
`GoodCo` or `BadCo`. However, another expectation should be that setting `type`
to `GoodCo` would correctly instantiate the object as a `Company::GoodCo`. That
second expectation is what this should fix.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add full set of MySQL CLI options to support SSL authentication when using db:structure dump and load
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
db:structure dump and load
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add more detailed comment about _assign_attribute method [ci skip]
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
fix minor problems
|
