diff options
| author | alexpdp7 <alex@pdp7.net> | 2025-02-21 15:03:13 +0000 |
|---|---|---|
| committer | alexpdp7 <alex@corcoles.net> | 2025-02-21 16:03:59 +0100 |
| commit | b1aa14fbfa8f7bca4f6c39ea50f4c7d65f7006f5 (patch) | |
| tree | a5d560b2b932567006282958a8784b4b685c054d /programming | |
| parent | 0b75d287038f26c2a1b19213e0a9cbe704b8f96b (diff) | |
Add note about database development command
Diffstat (limited to 'programming')
| -rw-r--r-- | programming/python/about_django.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/programming/python/about_django.md b/programming/python/about_django.md index b746801e..1cf3bd75 100644 --- a/programming/python/about_django.md +++ b/programming/python/about_django.md @@ -89,6 +89,10 @@ However, while developing a Django application, you frequently need to make many In my opinion, if you follow the Django documentation, then you might end up using migrations for those development schema changes. This is awkward and problematic, and there are procedures to develop database changes that work better. +I would like a command that recreates your database, applying unmigrated model changes. +This command could also have hooks to load sample data. +(Likely, Python code and not fixtures.) + ### Django only tackles database-based, server-side-rendered, non highly interactive web applications While certainly a huge amount of applications: |