14👍
✅
Yes, you can assume it is a standard rule that RDBMSes require an index for the primary key.
Mainly, the database engine needs the index to enforces data uniqueness for the primary key, and to do this quickly requires an index.
6👍
Have a look at this
If a PRIMARY KEY constraint is
created for a database table and no
clustered index currently exists for
that table, SQL Server automatically
creates a clustered index on the
primary key
- Best way to denormalize data in Django?
- Django 1.6 and django-registration: built-in authentication views not picked up
- Django Admin + FORCE_SCRIPT_NAME + Login redirects incorrectly
- Managing multiple settings.py files
- How do I implement markdown in Django 1.6 app?
- Django admin, extending admin with custom views
- Django + Forms: Dynamic choices for ChoiceField
- Ajax, CSRF and DELETE
- How to nginx virtual servers + fcgi for django?
- How do I reply to an email using the Python imaplib and include the original message?
4👍
It tends to be the case in most RDBMSs that a primary key is implemented as an index.
This is not a requirement per-se, but a (pretty much) obvious optimization.
👤Oded
- How do I get the actual object id in a Django admin page (inside formfield_for_foreignkey)?
- How do I construct a Django form with model objects in a Select widget?
- Accessing Django OneToOneField in templates?
- Django; AWS Elastic Beanstalk ERROR: Your WSGIPath refers to a file that does not exist
Source:stackexchange.com
