Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
7cee650d
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
7cee650d
编写于
4月 07, 2017
作者:
K
Kamil Trzcinski
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Update migrations
上级
21a7aed9
变更
4
隐藏空白更改
内联
并排
Showing
4 changed file
with
14 addition
and
45 deletion
+14
-45
db/migrate/20170407114956_add_ref_to_ci_trigger_schedule.rb
db/migrate/20170407114956_add_ref_to_ci_trigger_schedule.rb
+0
-22
db/migrate/20170407122426_add_active_to_ci_trigger_schedule.rb
...grate/20170407122426_add_active_to_ci_trigger_schedule.rb
+0
-22
db/migrate/20170407140450_add_index_to_next_run_at_and_active.rb
...ate/20170407140450_add_index_to_next_run_at_and_active.rb
+12
-0
db/schema.rb
db/schema.rb
+2
-1
未找到文件。
db/migrate/20170407114956_add_ref_to_ci_trigger_schedule.rb
浏览文件 @
7cee650d
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class
AddRefToCiTriggerSchedule
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
# Set this constant to true if this migration requires downtime.
DOWNTIME
=
false
# When a migration requires downtime you **must** uncomment the following
# constant and define a short and easy to understand explanation as to why the
# migration requires downtime.
# DOWNTIME_REASON = ''
# When using the methods "add_concurrent_index", "remove_concurrent_index" or
# "add_column_with_default" you must disable the use of transactions
# as these methods can not run in an existing transaction.
# When using "add_concurrent_index" or "remove_concurrent_index" methods make sure
# that either of them is the _only_ method called in the migration,
# any other changes should go in a separate migration.
# This ensures that upon failure _only_ the index creation or removing fails
# and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
# disable_ddl_transaction!
def
change
add_column
:ci_trigger_schedules
,
:ref
,
:string
end
...
...
db/migrate/20170407122426_add_active_to_ci_trigger_schedule.rb
浏览文件 @
7cee650d
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class
AddActiveToCiTriggerSchedule
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
# Set this constant to true if this migration requires downtime.
DOWNTIME
=
false
# When a migration requires downtime you **must** uncomment the following
# constant and define a short and easy to understand explanation as to why the
# migration requires downtime.
# DOWNTIME_REASON = ''
# When using the methods "add_concurrent_index", "remove_concurrent_index" or
# "add_column_with_default" you must disable the use of transactions
# as these methods can not run in an existing transaction.
# When using "add_concurrent_index" or "remove_concurrent_index" methods make sure
# that either of them is the _only_ method called in the migration,
# any other changes should go in a separate migration.
# This ensures that upon failure _only_ the index creation or removing fails
# and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
# disable_ddl_transaction!
def
change
add_column
:ci_trigger_schedules
,
:active
,
:boolean
end
...
...
db/migrate/20170407140450_add_index_to_next_run_at_and_active.rb
0 → 100644
浏览文件 @
7cee650d
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class
AddIndexToNextRunAtAndActive
<
ActiveRecord
::
Migration
include
Gitlab
::
Database
::
MigrationHelpers
DOWNTIME
=
false
def
change
add_index
:ci_trigger_schedules
,
[
:active
,
:next_run_at
]
end
end
db/schema.rb
浏览文件 @
7cee650d
...
...
@@ -11,7 +11,7 @@
#
# It's strongly recommended that you check this file into your version control system.
ActiveRecord
::
Schema
.
define
(
version:
201704071
22426
)
do
ActiveRecord
::
Schema
.
define
(
version:
201704071
40450
)
do
# These are extensions that must be enabled in order to support this database
enable_extension
"plpgsql"
...
...
@@ -315,6 +315,7 @@ ActiveRecord::Schema.define(version: 20170407122426) do
t
.
boolean
"active"
end
add_index
"ci_trigger_schedules"
,
[
"active"
,
"next_run_at"
],
name:
"index_ci_trigger_schedules_on_active_and_next_run_at"
,
using: :btree
add_index
"ci_trigger_schedules"
,
[
"next_run_at"
],
name:
"index_ci_trigger_schedules_on_next_run_at"
,
using: :btree
add_index
"ci_trigger_schedules"
,
[
"project_id"
],
name:
"index_ci_trigger_schedules_on_project_id"
,
using: :btree
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录