gitlab-org--gitlab-foss/lib/tasks
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
..
ci
gitlab Use rake db:reset instead of db:setup 2016-04-14 15:53:54 +02:00
migrate
.gitkeep
brakeman.rake
cache.rake
dev.rake
flay.rake
flog.rake
gemojione.rake
grape.rake
rubocop.rake
scss-lint.rake
services.rake
setup.rake
sidekiq.rake
spec.rake
spinach.rake
test.rake