diff options
| author | Simon Charette <charette.s@gmail.com> | 2025-04-28 22:46:13 -0400 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2025-04-30 10:53:39 -0300 |
| commit | 5d03c71b7a2256e776f134a7844c95f0f8f06c6d (patch) | |
| tree | 68ef28f72f3f1f2d3972ef80f5cdefa38e24b55e /docs | |
| parent | 7f6a5fbe2ef26d9970508d5a7236fe009ec274d0 (diff) | |
[5.2.x] Refs #36052, #32234 -- Removed create_test_table_with_composite_primary_key flag in favor of using CompositePrimaryKey.
Now that Django properly supports creating models with composite primary
keys, the tests should use a `CompositePrimaryKey` field instead of a
feature flag to inline backend specific SQL for creating a composite PK.
Specifcially, the inspectdb's test_composite_primary_key was adjusted to
use schema editor instead of per-backend raw SQL.
Backport of 4c75858135589f3a00e32eb4d476074536371a32 from main.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions