summaryrefslogtreecommitdiff
path: root/doc/development
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2016-04-14 15:53:54 +0200
committerYorick Peterse <yorickpeterse@gmail.com>2016-04-14 15:53:54 +0200
commita54af831bae023770bf9b2633cc45ec0d5f5a66a (patch)
tree73a49760298375202530c0cf383a4f304c2894e6 /doc/development
parentbadb35335086b90e2522ea2da767830f2f3ba9a7 (diff)
downloadgitlab-ce-a54af831bae023770bf9b2633cc45ec0d5f5a66a.tar.gz
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".
Diffstat (limited to 'doc/development')
-rw-r--r--doc/development/rake_tasks.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/rake_tasks.md b/doc/development/rake_tasks.md
index 9f3fd69fc4e..6d04b9590e6 100644
--- a/doc/development/rake_tasks.md
+++ b/doc/development/rake_tasks.md
@@ -9,7 +9,7 @@ bundle exec rake setup
```
The `setup` task is a alias for `gitlab:setup`.
-This tasks calls `db:setup` to create the database, calls `add_limits_mysql` that adds limits to the database schema in case of a MySQL database and finally it calls `db:seed_fu` to seed the database.
+This tasks calls `db:reset` to create the database, calls `add_limits_mysql` that adds limits to the database schema in case of a MySQL database and finally it calls `db:seed_fu` to seed the database.
Note: `db:setup` calls `db:seed` but this does nothing.
## Run tests