Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

django-models

/django-models

Projektuje i edytuje modele Django (5.2 LTS i 6.x): opcje pól, choices, ograniczenia w bazie, indeksy, on_delete, managery i zapytania bez problemu N+1.

Licencja
MIT
Ostatnia zmiana repozytorium
19.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 19.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Projektuje i edytuje modele Django (5.2 LTS i 6.x): opcje pól, choices, ograniczenia w bazie, indeksy, on_delete, managery i zapytania bez problemu N+1.

Oryginalny opis (EN)

Designs and edits Django models (Django 5.2 LTS and 6.x) with correct field options, choices, database constraints, indexes, on_delete behaviour, managers and query patterns that avoid N+1 queries. Use when adding a model or field, enforcing a business rule in the database, choosing on_delete, or reviewing models.py in a pull request.

Jak działa

  1. Steps
  2. Field choices
  3. Example
  4. ondelete
  5. Queries that scale
  6. Checks before you finish
Sekcje z nagłówków SKILL.md, w oryginale · 110 linii, 712 słów
Podgląd SKILL.md
---
name: django-models
description: Designs and edits Django models (Django 5.2 LTS and 6.x) with correct field options, choices, database constraints, indexes, on_delete behaviour, managers and query patterns that avoid N+1 queries. Use when adding a model or field, enforcing a business rule in the database, choosing on_delete, or reviewing models.py in a pull request.
license: MIT
---

# Django models

Check the version in `requirements*.txt`, `pyproject.toml` or `uv.lock` first. This skill targets Django 5.2 LTS and 6.x. Notes call out where they differ.

## Steps

1. Read the existing models in the app, and match their base class, naming, `Meta` style and timestamp fields.
2. Choose field types and options from the table below.
3. Put rules that must always hold into `Meta.constraints` as well as into `clean()` or a form.
4. Add an index for each new filter or ordering the code will run on a large table.
5. Pick `on_delete` deliberately for every `ForeignKey`.
6. Run `python manage.py makemigrations`, read the generated file, and run `python manage.py sqlmigrate <app> <number>` for anything touching a big table. The `django-migrations` skill covers safe rollout.

## Field choices

| Need | Use | Avoid |
|---|---|---|
| Optional text | `CharField(blank=True, default="")` | `null=True` on text, which gives two kinds of empty |
| Optional number, date or FK | `null=True, blank=True` | |
| Money | `DecimalField(max_digits=12, decimal_places=2)` or integer cents | `FloatField` |
| Fixed set of values | `models.TextChoices` / `IntegerChoices` | Free text plus validation in a form |
| Default set by the database | `db_default=Now()` | A Python default when rows are inserted outside Django |
| Created and updated times | `auto_now_add=True` / `auto_now=True` | Setting them by hand in `save()` |
| Public identifier | `UUIDField(default=uuid.uuid4, unique=True, editable=False)` | Exposing the integer primary key |

`blank` is for validation (forms, `full_clean`). `null` is for the database column. They are separate settings.

## Example

```python
import uuid
from django.conf import settings
from django.db import models
from django.db.models import Q
from django.db.models.functions import Now


class Order(models.Model):
    class Status(models.TextChoices):
        DRAFT = "draft", "Draft"
        PAID = "paid", "Paid"
        CANCELLED = "cancelled", "Cancelled"

    public_id = models.UUIDField(default=uuid.uuid4, unique=True, editable=False)
    customer = models.ForeignKey(
        settings.AUTH_USER_MODEL, on_delete=models.PROTECT, related_name="orders"
    )
    status = models.CharField(max_length=16, choices=Status, default=Status.DRAFT)
    total = models.DecimalField(max_digits=12, decimal_places=2)
    note = models.TextField(blank=True, default="")
    created_at = models.DateTimeField(db_default=Now())
    paid_at = models.DateTimeField(null=True, blank=True)

    class Meta:
        ordering = ["-created_at"]
        indexes = [
            models.Index(fields=["customer", "-created_at"], name="order_customer_created_idx"),
        ]
        constraints = [
            models.CheckConstraint(condition=Q(total__gte=0), name="order_total_non_negative"),
            models.CheckConstraint(
                condition=~Q(status="paid") | Q(paid_at__isnull=False),
                name="order_paid_has_paid_at",
            ),
            models.UniqueConstraint(
                fields=["customer"], condition=Q(status="draft"), name="order_one_draft_per_customer"
            ),
        ]

    def __str__(self):
        return f"Order {self.public_id}"
```

Version notes:
- `CheckConstraint` takes `condition=` on Django 5.1 and later. The older `check=` argument was deprecated in 5.1 and removed in 6.0.
- `choices=Status` (passing the enum class directly) works on 5.0 and later. Older code uses `Status.choices`.
- `db_default` needs 5.0 or later.
- Use `UniqueConstraint` instead of `unique_together`, which the docs mark as likely to be deprecated.

## on_delete

| Choice | Use when |
|---|---|
| `PROTECT` | The child is a record you must keep (orders, invoices) |
| `RESTRICT` | Like `PROTECT`, but allows the delete when the parent is also being removed by another cascade |
| `CASCADE` | The child has no meaning without the parent (line items of an order) |
| `SET_NULL` | The link is optional history (`null=True` required) |
| `SET_DEFAULT` / `SET(...)` | You reassign to a placeholder |
| `DO_NOTHING` | Only with a database-level rule you manage yourself |

`CASCADE` on a user foreign key deletes the user's data along with the account. Pick it on purpose. Django 6.1 adds database-level variants (`DB_CASCADE`, `DB_SET_NULL`, `DB_SET_DEFAULT`). Check the 6.1 release notes before you use them, since they skip Python signals.

## Queries that scale

- Use `select_related("customer")` for foreign keys and one-to-one fields you read in a loop. Use `prefetch_related("items")` for reverse and many-to-many relations.
- Use `exists()` to test for rows, `count()` to count them, and `values_list("id", flat=True)` when you only need ids.
- Use `update()` and `bulk_create()` for batch writes. They skip `save()` and signals, so check that nothing relies on those.
- Put reusable filters on a custom `QuerySet` and expose it with `objects = OrderQuerySet.as_manager()`.
- Wrap multi-row writes in `transaction.atomic()`.

## Checks before you finish

- Every rule that must always hold has a database constraint, and every constraint has a stable `name`.
- No `null=True` on `CharField` or `TextField` without a reason.
- Every `ForeignKey` has a deliberate `on_delete` and a `related_name`.
- New filters on large tables have an index.
- `__str__` is defined and doesn't trigger extra queries.
- `makemigrations --check` reports no missing migrations.

Wersje

RepozytoriumWynikLicencja
Ta strona · autohandai/skillpack-django100MIT
getsentry/sentry100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki 34a191e681e9 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 91django-orm-patterns
    Opisuje wzorce Django ORM: modele, zapytania i relacje w aplikacjach opartych na bazie danych.
  • 95django-orm-patterns
    Podpowiada wzorce ORM Django: definicje modeli, typy pól, menedżery, QuerySet, select_related, transakcje i indeksy.
  • 100ac-django
    Opisuje pisanie w Django 6.1 (z rozdziałem o Django 5.2 LTS) i opcjonalnie DRF: modele, migracje, transakcje, bezpieczeństwo, testowanie i narzędzia w stylu Fat Models.
  • 100django-idioms
    Opisuje wzorce Django i DRF: zapytania ORM, managery modeli, widoki klasowe, serializery, migracje i testy w pytest-django.
  • 100django-dev
    Prowadzi przez zakładanie projektu Django, modele, formularze i konfigurację ustawień z Dynaconf, według wzorca jeden plik na model i spójnego nazewnictwa.
  • 100django-expert
    Buduje aplikacje Django i API w Django REST Framework: modele z indeksami, optymalizuje zapytania ORM i konfiguruje uwierzytelnianie JWT.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.