Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
张重言
rails
提交
b9822cc3
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,发现更多精彩内容 >>
提交
b9822cc3
编写于
5月 31, 2013
作者:
G
Graham Madden
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
reword for grammar and clarity
上级
861ec91e
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
3 addition
and
3 deletion
+3
-3
guides/source/active_record_basics.md
guides/source/active_record_basics.md
+3
-3
未找到文件。
guides/source/active_record_basics.md
浏览文件 @
b9822cc3
...
...
@@ -62,9 +62,9 @@ may be necessary to write a lot of configuration code. This is particularly true
for ORM frameworks in general. However, if you follow the conventions adopted by
Rails, you'll need to write very little configuration (in some case no
configuration at all) when creating Active Record models. The idea is that if
you configure your applications in the very same way most of the time
s
then this
should be the default way.
In this case
s, explicit configuration would be needed
only in those cases where you can't follow the
conventions for any reas
on.
you configure your applications in the very same way most of the time then this
should be the default way.
Thu
s, explicit configuration would be needed
only in those cases where you can't follow the
standar conventi
on.
### Naming Conventions
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录