#22603: Reorganize code in django.db.backends
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Currently, database backends are split in modules inconsistently. For
example:
- in the base implementation, most classes are defined in __init__.py; in
actual backends, most classes are in base.py;
- in the base implementation, BaseDatabaseCreation and
BaseDatabaseSchemaEditor have their own modules while other classes are
defined in __init__.py;
- the postgresql backend has an operations.py, other backends don't.
It would be easier to make cross-backend changes if the code was organized
consistently.
Considering the size of the classes involved, I think we should put each
class it its own module.
--
Ticket URL: <https://code.djangoproject.com/ticket/22603>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.138e6bbe3ce8dddf7b4011a609661c5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
