Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
张重言
rails
提交
89595aff
R
rails
项目概览
张重言
/
rails
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
rails
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
未验证
提交
89595aff
编写于
11月 28, 2018
作者:
R
Rafael França
提交者:
GitHub
11月 28, 2018
浏览文件
操作
浏览文件
下载
差异文件
Merge pull request #34562 from ruralocity/active-record-query-docs-improvement
Improve ActiveRecord::Querying documentation [ci skip]
上级
17abc668
96f6a59d
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
9 addition
and
7 deletion
+9
-7
activerecord/lib/active_record/querying.rb
activerecord/lib/active_record/querying.rb
+9
-7
未找到文件。
activerecord/lib/active_record/querying.rb
浏览文件 @
89595aff
...
...
@@ -16,17 +16,17 @@ module Querying
delegate
:pluck
,
:pick
,
:ids
,
to: :all
# Executes a custom SQL query against your database and returns all the results. The results will
# be returned as an array
with columns requested
encapsulated as attributes of the model you call
# this method from.
If you call <tt>Product.find_by_sql</tt>
then the results will be returned in
# be returned as an array
, with the requested columns
encapsulated as attributes of the model you call
# this method from.
For example, if you call <tt>Product.find_by_sql</tt>,
then the results will be returned in
# a +Product+ object with the attributes you specified in the SQL query.
#
# If you call a complicated SQL query which spans multiple tables the columns specified by the
# If you call a complicated SQL query which spans multiple tables
,
the columns specified by the
# SELECT will be attributes of the model, whether or not they are columns of the corresponding
# table.
#
# The +sql+ parameter is a full SQL query as a string. It will be called as is
,
there will be
# no database agnostic conversions performed. This should be a last resort because using
, for example,
#
MySQL specific terms will lock you to using that particular database engine
or require you to
# The +sql+ parameter is a full SQL query as a string. It will be called as is
;
there will be
# no database agnostic conversions performed. This should be a last resort because using
#
database-specific terms will lock you into using that particular database engine,
or require you to
# change your call if you switch engines.
#
# # A simple SQL query spanning multiple tables
...
...
@@ -61,7 +61,9 @@ def find_by_sql(sql, binds = [], preparable: nil, &block)
# Returns the result of an SQL statement that should only include a COUNT(*) in the SELECT part.
# The use of this method should be restricted to complicated SQL queries that can't be executed
# using the ActiveRecord::Calculations class methods. Look into those before using this.
# using the ActiveRecord::Calculations class methods. Look into those before using this method,
# as it could lock you into a specific database engine or require a code change to switch
# database engines.
#
# Product.count_by_sql "SELECT COUNT(*) FROM sales s, customers c WHERE s.customer_id = c.id"
# # => 12
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录