avoid starimports readme. list of functions moved

don't use starimports so don't use them in examples. the second example for v2 is ok because there it is not clear which functions are needed.
I think the list of functions should be in the section of v2.
This commit is contained in:
nimaje 2015-12-07 21:42:07 +01:00
parent 33ae7a6073
commit 58645bdff9

View file

@ -59,6 +59,29 @@ $ build_abilities()
$ build moves()
etc...
```
## V2 Database setup
Start Django shell
```
$ python manage.py shell --settings=config.local
```
run the build script with
```
$ from data.v2.build import build_all
$ build_all()
```
Each time the build script is run it will iterate over each table in the database, wipe it and rewrite each row using the data found in data/v2/csv.
When building against sqlite we've heard it can take a ridiculously long time to finish building out the database. In this case you can set up just the portions of the db that you need.
```
$ from data.v2.build import *
$ build_languages()
$ build_abilities()
...
```
Heres a list of the data building functions
- build_languages()
- build_regions()
@ -87,29 +110,6 @@ Heres a list of the data building functions
- build_pal_parks()
## V2 Database setup
Start Django shell
```
$ python manage.py shell --settings=config.local
```
run the build script with
```
$ from data.v2.build import *
$ build_all()
```
Each time the build script is run it will iterate over each table in the database, wipe it and rewrite each row using the data found in data/v2/csv.
When building against sqlite we've heard it can take a ridiculously long time to finish building out the database. In this case you can set up just the portions of the db that you need.
```
$ from data.v2.build import *
$ build_languages()
$ build_abilities()
...
```
Here
## Contributing
All contributions are welcome: bug fixes, data contributions, recommendations.