#35549: The Model's Meta option managed doesn't do what the documentation says
it
should.
-------------------------------------+-------------------------------------
Reporter: Tobi DEGNON | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => invalid
* status: new => closed
Comment:
I cannot produce with the project you provided. Django creates a migration
to track the model but the underlying table is not created as documented.
{{{#!sql
SQLite version 3.37.0 2021-12-09 01:34:53
Enter ".help" for usage hints.
sqlite> SELECT * FROM django_migrations WHERE app = 'core';
18|core|0001_initial|2024-06-21 16:34:30.110518
sqlite> .tables
auth_group auth_user_user_permissions
auth_group_permissions django_admin_log
auth_permission django_content_type
auth_user django_migrations
auth_user_groups django_session
}}}
`sqlmigrate` is coherent with that
{{{#!bash
$ ./manage.py sqlmigrate core 0001
BEGIN;
--
-- Create model Book
--
-- (no-op)
COMMIT;
}}}
There is a difference between creating a migration for tracking purposes
and actually creating a table on migration.
Please see TicketClosingReasons/UseSupportChannels for further support.
--
Ticket URL: <https://code.djangoproject.com/ticket/35549#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701903bab2dd2-e5333520-8c48-4bd7-8cb8-f788c5014591-000000%40eu-central-1.amazonses.com.
