gitlab-org--gitlab-foss/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
bulk_add_permission.rake
check.rake
cleanup.rake
db.rake
generate_docs.rake
git.rake
import.rake
info.rake
list_repos.rake
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
test.rake
two_factor.rake
update_commit_count.rake
web_hook.rake