2đź‘Ť
Answer: you should care, but not at first (usually).
Django doesn’t take care of everything for you, only the basic/initial indexes (if you use migration tool and not creating the tables manually).
The index is related to the actual data that will be stored in the table, not only the table structure, somthing that is not known by django during the tables creation. Some indexs you get for “free”, by creating unique constraints etc. (assuming you use tools like south that does that for you) but not real optimizations – this you’ll have to do on your own when the time comes.
Some optimizations can be done by “telling” Django which indexes should be added, but you will have to specify it yourself.
0đź‘Ť
No, Django only creates indices required by the database system, for example when creating foreign keys. You will have to optimise your database yourself, more on that in the documentation.
- Getting javascript array from django json dumped dictionary
- Django 1.9.9 cannot import name HAS_GEOIP
0đź‘Ť
You can tell Django that certain model fields should be used as an index:
https://docs.djangoproject.com/en/1.10/ref/models/fields/#django.db.models.Field.db_index
You can also index columns together:
https://docs.djangoproject.com/en/1.10/ref/models/options/#django.db.models.Options.index_together
-1đź‘Ť
Yes, you are right…with Django you can generate your database from your model (classes), you have to use specifics inheritance and types but it’s pretty easy to handle and of course it’s as optimal as could be needed.
- Django – Lettuce – Selenium
- Python Django : item title does not show
- Django ORM, accessing the attributes of relationships
- Django error: Reverse for 'details' with arguments '()' and keyword arguments
- Django DRF serializer on PrimaryKeyRelatedField