Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
1a8dc206
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,发现更多精彩内容 >>
未验证
提交
1a8dc206
编写于
5月 04, 2017
作者:
L
Luke "Jared" Bennett
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Reset migration to head
上级
d34f6764
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
0 addition
and
98 deletion
+0
-98
db/migrate/20170428123910_add_clientside_sentry_to_application_settings.rb
...28123910_add_clientside_sentry_to_application_settings.rb
+0
-31
db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb
...04094058_add_clientside_sentry_to_application_settings.rb
+0
-65
db/schema.rb
db/schema.rb
+0
-2
未找到文件。
db/migrate/20170428123910_add_clientside_sentry_to_application_settings.rb
已删除
100644 → 0
浏览文件 @
d34f6764
class
AddClientsideSentryToApplicationSettings
<
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" 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" make sure that this
# method 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 fails and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
disable_ddl_transaction!
def
up
add_column_with_default
:application_settings
,
:clientside_sentry_enabled
,
:boolean
,
default:
false
add_column
:application_settings
,
:clientside_sentry_dsn
,
:string
end
def
down
remove_columns
:application_settings
,
:clientside_sentry_enabled
,
:clientside_sentry_dsn
end
end
db/migrate/20170504094058_add_clientside_sentry_to_application_settings.rb
已删除
100644 → 0
浏览文件 @
d34f6764
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
class
AddClientsideSentryToApplicationSettings
<
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!
# Reversability was tested when I made an update the originally irreversible
# migration after I ran it, so I could test that the down method worked and then
# the up method worked.
def
up
add_column_with_default
:application_settings
,
:clientside_sentry_enabled
,
:boolean
,
default:
false
add_column
:application_settings
,
:clientside_sentry_dsn
,
:string
end
def
down
remove_columns
:application_settings
,
:clientside_sentry_enabled
,
:clientside_sentry_dsn
end
end
class
AddClientsideSentryToApplicationSettings
<
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" 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" make sure that this
# method 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 fails and can be retried or reverted easily.
#
# To disable transactions uncomment the following line and remove these
# comments:
disable_ddl_transaction!
end
db/schema.rb
浏览文件 @
1a8dc206
...
...
@@ -121,8 +121,6 @@ ActiveRecord::Schema.define(version: 20170502091007) do
t
.
integer
"cached_markdown_version"
t
.
boolean
"usage_ping_enabled"
,
default:
true
,
null:
false
t
.
string
"uuid"
t
.
boolean
"clientside_sentry_enabled"
,
default:
false
,
null:
false
t
.
string
"clientside_sentry_dsn"
end
create_table
"audit_events"
,
force: :cascade
do
|
t
|
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录