gitlab-ce/lib/tasks/gitlab
Yorick Peterse a54af831ba
Use rake db:reset instead of db:setup
Using db:reset ensures existing tables are first dropped. This in turn
ensures that we can drop tables regardless of any foreign key
constraints. While CE currently doesn't have any foreign keys EE defines
the following relation:

    remote_mirrors.project_id -> projects.id

MySQL will complain whenever you try to drop the "projects" table first
even when using "DROP TABLE ... CASCADE".
2016-04-14 15:53:54 +02:00
..
backup.rake Reload the schema before restoring a database backup 2016-03-21 21:16:34 -05:00
bulk_add_permission.rake
check.rake Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature 2016-03-25 13:05:15 +01:00
cleanup.rake
db.rake Reload the schema before restoring a database backup 2016-03-21 21:16:34 -05:00
generate_docs.rake
git.rake
import.rake Update project repository size and commit count during import:repos task 2015-12-08 09:08:22 -08:00
info.rake
list_repos.rake Detect project and namespace changes in list:repos 2015-12-08 16:06:06 +01:00
setup.rake Use rake db:reset instead of db:setup 2016-04-14 15:53:54 +02:00
shell.rake
sidekiq.rake
task_helpers.rake Prevent StateMachine warnings from outputting during a cron task 2016-01-15 17:47:56 -05:00
test.rake
two_factor.rake
update_commit_count.rake
web_hook.rake web hooks to webhooks 2016-03-10 14:48:29 -05:00