| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(#35612)
* Add example for has_many :through source/source_type
* Add example for has_one :through source/source_type
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* s/Postgres/PostgreSQL/
* s/MYSQL/MySQL/, s/Mysql/MySQL/
* s/Sqlite/SQLite/
Replaced all newly added them after 6089b31.
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
url -> URL in Action Cable guide [ci skip]
|
| | | | |
|
|/ / / |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Failing test case
* feat: Dynamic Url Generation
Change createWebSocketURL to be a closure that allows url to be evaluated at the time the webSocket is established
* refactor: createWebSocketURL to Consumer, remove need for closure
Move initial call to createWebSocketURL in createConsumer
* docs: Add documentation for dynamic url and string args to createConsumer
Co-Authored-By: rmacklin <rmacklin@users.noreply.github.com>
[Ryan Castner, rmacklin]
|
|\ \
| | |
| | |
| | |
| | | |
abhaynikam/35752-update-migration-doc-column-identifier
[ci skip] Updated docs to reflect index: true option not available as column modifier
|
| | |
| | |
| | |
| | | |
modifier
|
|/ /
| |
| |
| | |
active_record_querying.md
|
|\ \
| | |
| | | |
Rename `i18n_full_message` config option to `i18n_customize_full_message`
|
| | |
| | |
| | |
| | |
| | |
| | | |
- I feel `i18n_customize_full_messages` explains the meaning of the
config better.
- Followup of https://github.com/rails/rails/pull/32956
|
|/ / |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
* Update active_record_migrations.md
* Change year to match others
[Ken Greeff + Rafael Mendonça França]
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
[ci skip] (#35733)
|
|\
| |
| | |
Add config.disable_sandbox option to Rails console
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A long-running `rails console --sandbox` could cause a database server
to become out-of-memory as it's holding on to changes that happen on the
database.
Given that it's common for Ruby on Rails application with huge
traffic to have separate write database and read database, we should
allow the developers to disable this sandbox option to prevent someone
from accidentally causing the Denial-of-Service on their server.
|
|\ \
| | |
| | | |
Add `unknown` method to list of methods to write current log [ci skip]
|
| |/ |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
localhostdotdev/fix-rails-guides-generation-invalid-formats-html
Fix rails guides generation
|
| |/
| |
| |
| | |
Was getting `formats=': Invalid formats: "html"
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch has two main portions:
1. Add SQL comment support to Arel via Arel::Nodes::Comment.
2. Implement a Relation#annotate method on top of that.
== Adding SQL comment support
Adds a new Arel::Nodes::Comment node that represents an optional SQL
comment and teachers the relevant visitors how to handle it.
Comment nodes may be added to the basic CRUD statement nodes and set
through any of the four (Select|Insert|Update|Delete)Manager objects.
For example:
manager = Arel::UpdateManager.new
manager.table table
manager.comment("annotation")
manager.to_sql # UPDATE "users" /* annotation */
This new node type will be used by ActiveRecord::Relation to enable
query annotation via SQL comments.
== Implementing the Relation#annotate method
Implements `ActiveRecord::Relation#annotate`, which accepts a comment
string that will be appeneded to any queries generated by the relation.
Some examples:
relation = Post.where(id: 123).annotate("metadata string")
relation.first
# SELECT "posts".* FROM "posts" WHERE "posts"."id" = 123
# LIMIT 1 /* metadata string */
class Tag < ActiveRecord::Base
scope :foo_annotated, -> { annotate("foo") }
end
Tag.foo_annotated.annotate("bar").first
# SELECT "tags".* FROM "tags" LIMIT 1 /* foo */ /* bar */
Also wires up the plumbing so this works with `#update_all` and
`#delete_all` as well.
This feature is useful for instrumentation and general analysis of
queries generated at runtime.
|
|
|
|
|
| |
We added ActiveSupport::Notifications instrumentation of the processing of each middleware in the stack,
See 04ae0b0b5e594e0bb99c5cd608921745977bcdcd.
|
|
|
|
| |
generators""
|
| |
|
|
|
| |
[Alex Kitchens, Prathamesh Sonpatki]
|
|
|
|
|
|
| |
These are introduced after Rails 6.0.0 beta2.
[ci skip]
|
|
|
|
| |
See #33912.
|
|\
| |
| |
| | |
v6.0.0.beta3 release
|
| |
| |
| |
| |
| |
| |
| | |
* Update RAILS_VERSION
* Bundle
* rake update_versions
* rake changelog:header
|
|\ \
| | |
| | | |
Fix warnings from Guides generation
|
| | |
| | |
| | |
| | |
| | |
| | | |
https://github.com/rails/rails/pull/35036 AV warns about not having the compiled container.
Use the suggested with_empty_template_cache to overcome warning
|
|\ \ \
| |/ /
|/| | |
Add note about has_many associations callbacks [ci skip]
|
| | |
| | |
| | |
| | | |
Add a note explaining when the has_many associations callbacks will be called or not.
|
|\ \ \
| | | |
| | | | |
Add `config.credentials.content_path` and `config.credentials.key_path` to the guide
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the guide
- Fix some typos
Follow up #33962
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[ci skip]
- Instead of the note at the end, added an example of how the output
looks by using the expanded switch.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
abhaynikam/35492-follow-up-to-updates-links-to-https
Updated links from http to https in guides, docs, etc
|
| | |/ /
| |/| | |
|
| | | | |
|