plain.postgres 0.113.2__tar.gz → 0.114.0__tar.gz

{plain_postgres-0.113.2 → plain_postgres-0.114.0}/PKG-INFO

@@ -1,12 +1,12 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: plain.postgres
-Version: 0.113.2
+Version: 0.114.0
 Summary: Model your data and store it in a database.
 Author-email: Dave Gaeddert <dave.gaeddert@dropseed.dev>
 License-Expression: BSD-3-Clause
 License-File: LICENSE
 Requires-Python: >=3.13
-Requires-Dist: plain<1.0.0,>=0.134.0
+Requires-Dist: plain<1.0.0,>=0.157.0
 Requires-Dist: psycopg-pool>=3.2
 Requires-Dist: psycopg>=3.2
 Description-Content-Type: text/markdown
@@ -179,9 +179,8 @@ user = User.query.get(email="test@example.com")
 
 # Complex queries with Q objects
 from plain.postgres import Q
-users = User.query.filter(
-    Q(is_admin=True) | Q(email__endswith="@example.com")
-)
+
+users = User.query.filter(Q(is_admin=True) | Q(email__endswith="@example.com"))
 
 # Ordering
 users = User.query.order_by("-created_at")
@@ -200,6 +199,7 @@ You can customize [`QuerySet`](./query.py#QuerySet) classes to provide specializ
 from typing import Self
 from plain.postgres import types
 
+
 class PublishedQuerySet(postgres.QuerySet["Article"]):
     def published_only(self) -> Self:
         return self.filter(status="published")
@@ -207,6 +207,7 @@ class PublishedQuerySet(postgres.QuerySet["Article"]):
     def draft_only(self) -> Self:
         return self.filter(status="draft")
 
+
 @postgres.register_model
 class Article(postgres.Model):
     title: str = types.TextField(max_length=200)
@@ -214,6 +215,7 @@ class Article(postgres.Model):
 
     query = PublishedQuerySet()
 
+
 # Usage - all methods available on Article.query
 all_articles = Article.query.all()
 published_articles = Article.query.published_only()
@@ -239,6 +241,7 @@ from __future__ import annotations
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class User(postgres.Model):
     email: str = types.EmailField()
@@ -256,11 +259,14 @@ For complex queries that can't be expressed with the ORM, you can use raw SQL.
 Use `Model.query.raw()` to execute raw SQL and get model instances back:
 
 ```python
-users = User.query.raw("""
+users = User.query.raw(
+    """
     SELECT * FROM users
     WHERE created_at > %s
     ORDER BY created_at DESC
-""", [some_date])
+""",
+    [some_date],
+)
 
 for user in users:
     print(user.email)  # Full model instance with all fields
@@ -333,6 +339,7 @@ for category in Category.query.all():
 
 # Good — single query with annotation
 from plain.postgres.aggregates import Count
+
 for category in Category.query.annotate(num_products=Count("products")).all():
     print(category.num_products)
 ```
@@ -346,6 +353,7 @@ Templates should only render data, never trigger queries. Prepare everything in
 def get_template_context(self):
     return {"posts": Post.query.all()}  # related lookups happen in template
 
+
 # Good — eagerly load everything
 def get_template_context(self):
     return {"posts": Post.query.select_related("author").prefetch_related("tags").all()}
@@ -369,10 +377,12 @@ emails = list(User.query.values_list("email", flat=True))
 
 ```python
 # Bad
-if User.query.filter(is_active=True).count() > 0: ...
+if User.query.filter(is_active=True).count() > 0:
+    ...
 
 # Good
-if User.query.filter(is_active=True).exists(): ...
+if User.query.filter(is_active=True).exists():
+    ...
 ```
 
 #### Use `.count()` instead of `len(queryset)`
@@ -479,8 +489,8 @@ Run a block of code in a read-only transaction using `read_only()`. Any write (I
 from plain.postgres.db import read_only
 
 with read_only():
-    users = User.query.all()       # reads work
-    User.query.create(name="x")   # raises psycopg.errors.ReadOnlySqlTransaction
+    users = User.query.all()  # reads work
+    User.query.create(name="x")  # raises psycopg.errors.ReadOnlySqlTransaction
 ```
 
 `read_only()` opens a single `BEGIN READ ONLY` transaction for the block. Nested `atomic()` blocks inside become savepoints of the outer read-only transaction and inherit read-only.
@@ -493,10 +503,10 @@ Because the whole block is one transaction, catching a database error inside `re
 with read_only():
     try:
         with atomic():
-            User.query.create(name="x")   # raises, savepoint rolls back
+            User.query.create(name="x")  # raises, savepoint rolls back
     except psycopg.errors.ReadOnlySqlTransaction:
         pass
-    User.query.count()   # still works — outer txn is healthy
+    User.query.count()  # still works — outer txn is healthy
 ```
 
 ## Schema management
@@ -718,7 +728,9 @@ class User(postgres.Model):
         ],
         constraints=[
             postgres.UniqueConstraint(fields=["email"], name="users_email_uniq"),
-            postgres.CheckConstraint(check=postgres.Q(age__gte=0), name="users_age_positive"),
+            postgres.CheckConstraint(
+                check=postgres.Q(age__gte=0), name="users_age_positive"
+            ),
         ],
     )
 ```
@@ -819,6 +831,7 @@ from datetime import datetime
 from plain import postgres
 from plain.postgres import types
 
+
 class Product(postgres.Model):
     # Text fields
     name: str = types.TextField(max_length=200)
@@ -923,6 +936,7 @@ This is **not** for passwords or tokens you issue — those should be hashed (on
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Integration(postgres.Model):
     name: str = types.TextField(max_length=100)
@@ -959,6 +973,7 @@ Use [`ForeignKeyField`](./fields/related.py#ForeignKeyField) for many-to-one and
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Book(postgres.Model):
     title: str = types.TextField(max_length=200)
@@ -972,9 +987,9 @@ Accessing a foreign key gives you the related object without a query — only it
 
 ```python
 book = Book.query.get(id=1)
-book.author        # no query — a partial Author instance
-book.author.id     # no query — the foreign key value
-book.author.name   # one query — loads the rest of the row
+book.author  # no query — a partial Author instance
+book.author.id  # no query — the foreign key value
+book.author.name  # one query — loads the rest of the row
 ```
 
 The first access to any non-key field loads the whole row in a single query. There is no separate `author_id` attribute — `book.author.id` is the foreign key value, and it is type-checked because `book.author` is an `Author`. In loops, use `select_related()` to load related rows up front and avoid a query per row.
@@ -989,17 +1004,20 @@ When you define a `ForeignKey` or `ManyToManyField`, Plain automatically creates
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Author(postgres.Model):
     name: str = types.TextField(max_length=200)
     # Explicit reverse accessor for all books by this author
     books = types.ReverseForeignKey(to="Book", field="author")
 
+
 @postgres.register_model
 class Book(postgres.Model):
     title: str = types.TextField(max_length=200)
     author: Author = types.ForeignKeyField(Author, on_delete=postgres.CASCADE)
 
+
 # Usage
 author = Author.query.get(name="Jane Doe")
 for book in author.books.all():
@@ -1018,11 +1036,13 @@ class Feature(postgres.Model):
     # Explicit reverse accessor for all cars with this feature
     cars = types.ReverseManyToMany(to="Car", field="features")
 
+
 @postgres.register_model
 class Car(postgres.Model):
     model: str = types.TextField(max_length=100)
     features = types.ManyToManyField(Feature)
 
+
 # Usage
 feature = Feature.query.get(name="Sunroof")
 for car in feature.cars.all():
@@ -1042,10 +1062,14 @@ To get type checking for custom QuerySet methods on reverse relations, specify t
 
 ```python
 # Basic usage
-books: types.ReverseForeignKey[Book] = types.ReverseForeignKey(to="Book", field="author")
+books: types.ReverseForeignKey[Book] = types.ReverseForeignKey(
+    to="Book", field="author"
+)
 
 # With custom QuerySet for proper method recognition
-books: types.ReverseForeignKey[Book, BookQuerySet] = types.ReverseForeignKey(to="Book", field="author")
+books: types.ReverseForeignKey[Book, BookQuerySet] = types.ReverseForeignKey(
+    to="Book", field="author"
+)
 
 # Now type checkers recognize custom methods like .published()
 author.books.query.published()
@@ -1189,6 +1213,7 @@ class Order(postgres.Model):
     status: str = types.TextField(max_length=20)
     created_at: datetime = types.DateTimeField()
 
+
 # Good — indexed for common queries
 class Order(postgres.Model):
     status: str = types.TextField(max_length=20)
@@ -1210,6 +1235,7 @@ def create(self):
         raise ValueError("duplicate")
     return super().create()
 
+
 # Good — database-enforced
 model_options = postgres.Options(
     constraints=[postgres.UniqueConstraint(fields=["email"])],
@@ -1222,7 +1248,9 @@ CASCADE for owned children, RESTRICT for referenced data, SET_NULL for optional
 
 ```python
 # Bad — blindly using CASCADE everywhere
-company: Company = types.ForeignKeyField("Company", on_delete=postgres.CASCADE)  # deleting company deletes invoices!
+company: Company = types.ForeignKeyField(
+    "Company", on_delete=postgres.CASCADE
+)  # deleting company deletes invoices!
 
 # Good — block the delete while invoices reference the company
 company: Company = types.ForeignKeyField("Company", on_delete=postgres.RESTRICT)
@@ -1248,10 +1276,12 @@ Models integrate with [plain.forms](../../../plain-forms/plain/forms/README.md):
 from plain import forms
 from .models import User
 
+
 class UserForm(forms.ModelForm):
     class Meta:
         model = User
-        fields = ["email", "is_admin"]
+        fields = ("email", "is_admin")
+
 
 # Usage
 form = UserForm(request=request)
@@ -1512,7 +1542,9 @@ Use `UniqueConstraint` in your model's `model_options`:
 ```python
 model_options = postgres.Options(
     constraints=[
-        postgres.UniqueConstraint(fields=["email", "organization"], name="unique_email_per_org"),
+        postgres.UniqueConstraint(
+            fields=["email", "organization"], name="unique_email_per_org"
+        ),
     ],
 )
 ```

{plain_postgres-0.113.2 → plain_postgres-0.114.0}/plain/postgres/CHANGELOG.md

@@ -1,5 +1,22 @@
 # plain-postgres changelog
 
+## [0.114.0](https://github.com/dropseed/plain/releases/plain-postgres@0.114.0) (2026-08-12)
+
+### What's changed
+
+- Wrong-type arguments now raise `TypeError` instead of `ValueError` across the schema and query APIs: `UniqueConstraint`/`Index` options (`condition`, `deferrable`, `include`, `opclasses`, `fields`), `Extract`/`Trunc` field types, non-bool `isnull` lookups, `RunPython` without a callable, serializer registration, assigning a wrong-model instance (or bool) to a foreign key, and reverse descriptors on non-FK/M2M fields ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+- `Migration.operations`/`dependencies`/`replaces` are typed as `Sequence`, and `plain migrations create` now writes them as tuples in generated files. Existing list-based migration files keep working ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+- Migration filename timestamps use the app's `TIME_ZONE` (via `timezone.localtime()`) instead of the machine's local clock, so a team generates consistently named migrations ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+- Model field `default_validators` is now a tuple and `empty_values` a tuple; `ignored_tables` on the connection is a tuple ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+- `ModelsRegistry.get_models()` caching was reworked to a per-instance memo (still cleared by `clear_cache()`), replacing a `functools.cache` keyed on the registry instance ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+- `on_commit()` handler errors are logged with `logger.exception()` — same message and traceback, standard idiom ([f52e18f532](https://github.com/dropseed/plain/commit/f52e18f532))
+
+### Upgrade instructions
+
+- If you catch `ValueError` around any of the argument-validation cases above, catch `TypeError` instead
+- Newly generated migrations use tuples for `dependencies`/`operations`; existing migration files don't need to change
+- Requires `plain>=0.157.0`
+
 ## [0.113.2](https://github.com/dropseed/plain/releases/plain-postgres@0.113.2) (2026-08-10)
 
 ### What's changed
@@ -408,7 +425,11 @@
 
     ```python
     # Before
-    from plain.postgres.connections import get_connection, read_only, use_management_connection
+    from plain.postgres.connections import (
+        get_connection,
+        read_only,
+        use_management_connection,
+    )
 
     # After
     from plain.postgres.db import get_connection, read_only, use_management_connection

{plain_postgres-0.113.2 → plain_postgres-0.114.0}/plain/postgres/README.md

@@ -166,9 +166,8 @@ user = User.query.get(email="test@example.com")
 
 # Complex queries with Q objects
 from plain.postgres import Q
-users = User.query.filter(
-    Q(is_admin=True) | Q(email__endswith="@example.com")
-)
+
+users = User.query.filter(Q(is_admin=True) | Q(email__endswith="@example.com"))
 
 # Ordering
 users = User.query.order_by("-created_at")
@@ -187,6 +186,7 @@ You can customize [`QuerySet`](./query.py#QuerySet) classes to provide specializ
 from typing import Self
 from plain.postgres import types
 
+
 class PublishedQuerySet(postgres.QuerySet["Article"]):
     def published_only(self) -> Self:
         return self.filter(status="published")
@@ -194,6 +194,7 @@ class PublishedQuerySet(postgres.QuerySet["Article"]):
     def draft_only(self) -> Self:
         return self.filter(status="draft")
 
+
 @postgres.register_model
 class Article(postgres.Model):
     title: str = types.TextField(max_length=200)
@@ -201,6 +202,7 @@ class Article(postgres.Model):
 
     query = PublishedQuerySet()
 
+
 # Usage - all methods available on Article.query
 all_articles = Article.query.all()
 published_articles = Article.query.published_only()
@@ -226,6 +228,7 @@ from __future__ import annotations
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class User(postgres.Model):
     email: str = types.EmailField()
@@ -243,11 +246,14 @@ For complex queries that can't be expressed with the ORM, you can use raw SQL.
 Use `Model.query.raw()` to execute raw SQL and get model instances back:
 
 ```python
-users = User.query.raw("""
+users = User.query.raw(
+    """
     SELECT * FROM users
     WHERE created_at > %s
     ORDER BY created_at DESC
-""", [some_date])
+""",
+    [some_date],
+)
 
 for user in users:
     print(user.email)  # Full model instance with all fields
@@ -320,6 +326,7 @@ for category in Category.query.all():
 
 # Good — single query with annotation
 from plain.postgres.aggregates import Count
+
 for category in Category.query.annotate(num_products=Count("products")).all():
     print(category.num_products)
 ```
@@ -333,6 +340,7 @@ Templates should only render data, never trigger queries. Prepare everything in
 def get_template_context(self):
     return {"posts": Post.query.all()}  # related lookups happen in template
 
+
 # Good — eagerly load everything
 def get_template_context(self):
     return {"posts": Post.query.select_related("author").prefetch_related("tags").all()}
@@ -356,10 +364,12 @@ emails = list(User.query.values_list("email", flat=True))
 
 ```python
 # Bad
-if User.query.filter(is_active=True).count() > 0: ...
+if User.query.filter(is_active=True).count() > 0:
+    ...
 
 # Good
-if User.query.filter(is_active=True).exists(): ...
+if User.query.filter(is_active=True).exists():
+    ...
 ```
 
 #### Use `.count()` instead of `len(queryset)`
@@ -466,8 +476,8 @@ Run a block of code in a read-only transaction using `read_only()`. Any write (I
 from plain.postgres.db import read_only
 
 with read_only():
-    users = User.query.all()       # reads work
-    User.query.create(name="x")   # raises psycopg.errors.ReadOnlySqlTransaction
+    users = User.query.all()  # reads work
+    User.query.create(name="x")  # raises psycopg.errors.ReadOnlySqlTransaction
 ```
 
 `read_only()` opens a single `BEGIN READ ONLY` transaction for the block. Nested `atomic()` blocks inside become savepoints of the outer read-only transaction and inherit read-only.
@@ -480,10 +490,10 @@ Because the whole block is one transaction, catching a database error inside `re
 with read_only():
     try:
         with atomic():
-            User.query.create(name="x")   # raises, savepoint rolls back
+            User.query.create(name="x")  # raises, savepoint rolls back
     except psycopg.errors.ReadOnlySqlTransaction:
         pass
-    User.query.count()   # still works — outer txn is healthy
+    User.query.count()  # still works — outer txn is healthy
 ```
 
 ## Schema management
@@ -705,7 +715,9 @@ class User(postgres.Model):
         ],
         constraints=[
             postgres.UniqueConstraint(fields=["email"], name="users_email_uniq"),
-            postgres.CheckConstraint(check=postgres.Q(age__gte=0), name="users_age_positive"),
+            postgres.CheckConstraint(
+                check=postgres.Q(age__gte=0), name="users_age_positive"
+            ),
         ],
     )
 ```
@@ -806,6 +818,7 @@ from datetime import datetime
 from plain import postgres
 from plain.postgres import types
 
+
 class Product(postgres.Model):
     # Text fields
     name: str = types.TextField(max_length=200)
@@ -910,6 +923,7 @@ This is **not** for passwords or tokens you issue — those should be hashed (on
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Integration(postgres.Model):
     name: str = types.TextField(max_length=100)
@@ -946,6 +960,7 @@ Use [`ForeignKeyField`](./fields/related.py#ForeignKeyField) for many-to-one and
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Book(postgres.Model):
     title: str = types.TextField(max_length=200)
@@ -959,9 +974,9 @@ Accessing a foreign key gives you the related object without a query — only it
 
 ```python
 book = Book.query.get(id=1)
-book.author        # no query — a partial Author instance
-book.author.id     # no query — the foreign key value
-book.author.name   # one query — loads the rest of the row
+book.author  # no query — a partial Author instance
+book.author.id  # no query — the foreign key value
+book.author.name  # one query — loads the rest of the row
 ```
 
 The first access to any non-key field loads the whole row in a single query. There is no separate `author_id` attribute — `book.author.id` is the foreign key value, and it is type-checked because `book.author` is an `Author`. In loops, use `select_related()` to load related rows up front and avoid a query per row.
@@ -976,17 +991,20 @@ When you define a `ForeignKey` or `ManyToManyField`, Plain automatically creates
 from plain import postgres
 from plain.postgres import types
 
+
 @postgres.register_model
 class Author(postgres.Model):
     name: str = types.TextField(max_length=200)
     # Explicit reverse accessor for all books by this author
     books = types.ReverseForeignKey(to="Book", field="author")
 
+
 @postgres.register_model
 class Book(postgres.Model):
     title: str = types.TextField(max_length=200)
     author: Author = types.ForeignKeyField(Author, on_delete=postgres.CASCADE)
 
+
 # Usage
 author = Author.query.get(name="Jane Doe")
 for book in author.books.all():
@@ -1005,11 +1023,13 @@ class Feature(postgres.Model):
     # Explicit reverse accessor for all cars with this feature
     cars = types.ReverseManyToMany(to="Car", field="features")
 
+
 @postgres.register_model
 class Car(postgres.Model):
     model: str = types.TextField(max_length=100)
     features = types.ManyToManyField(Feature)
 
+
 # Usage
 feature = Feature.query.get(name="Sunroof")
 for car in feature.cars.all():
@@ -1029,10 +1049,14 @@ To get type checking for custom QuerySet methods on reverse relations, specify t
 
 ```python
 # Basic usage
-books: types.ReverseForeignKey[Book] = types.ReverseForeignKey(to="Book", field="author")
+books: types.ReverseForeignKey[Book] = types.ReverseForeignKey(
+    to="Book", field="author"
+)
 
 # With custom QuerySet for proper method recognition
-books: types.ReverseForeignKey[Book, BookQuerySet] = types.ReverseForeignKey(to="Book", field="author")
+books: types.ReverseForeignKey[Book, BookQuerySet] = types.ReverseForeignKey(
+    to="Book", field="author"
+)
 
 # Now type checkers recognize custom methods like .published()
 author.books.query.published()
@@ -1176,6 +1200,7 @@ class Order(postgres.Model):
     status: str = types.TextField(max_length=20)
     created_at: datetime = types.DateTimeField()
 
+
 # Good — indexed for common queries
 class Order(postgres.Model):
     status: str = types.TextField(max_length=20)
@@ -1197,6 +1222,7 @@ def create(self):
         raise ValueError("duplicate")
     return super().create()
 
+
 # Good — database-enforced
 model_options = postgres.Options(
     constraints=[postgres.UniqueConstraint(fields=["email"])],
@@ -1209,7 +1235,9 @@ CASCADE for owned children, RESTRICT for referenced data, SET_NULL for optional
 
 ```python
 # Bad — blindly using CASCADE everywhere
-company: Company = types.ForeignKeyField("Company", on_delete=postgres.CASCADE)  # deleting company deletes invoices!
+company: Company = types.ForeignKeyField(
+    "Company", on_delete=postgres.CASCADE
+)  # deleting company deletes invoices!
 
 # Good — block the delete while invoices reference the company
 company: Company = types.ForeignKeyField("Company", on_delete=postgres.RESTRICT)
@@ -1235,10 +1263,12 @@ Models integrate with [plain.forms](../../../plain-forms/plain/forms/README.md):
 from plain import forms
 from .models import User
 
+
 class UserForm(forms.ModelForm):
     class Meta:
         model = User
-        fields = ["email", "is_admin"]
+        fields = ("email", "is_admin")
+
 
 # Usage
 form = UserForm(request=request)
@@ -1499,7 +1529,9 @@ Use `UniqueConstraint` in your model's `model_options`:
 ```python
 model_options = postgres.Options(
     constraints=[
-        postgres.UniqueConstraint(fields=["email", "organization"], name="unique_email_per_org"),
+        postgres.UniqueConstraint(
+            fields=["email", "organization"], name="unique_email_per_org"
+        ),
     ],
 )
 ```

{plain_postgres-0.113.2 → plain_postgres-0.114.0}/plain/postgres/__init__.py

@@ -56,65 +56,47 @@ from . import types
 # Advanced query-time features (aggregates, expressions, etc.) should be
 # imported from their specific modules (e.g., plain.postgres.aggregates).
 __all__ = [
-    # From constraints
-    "CheckConstraint",
-    "UniqueConstraint",
-    # From enums
-    "TextChoices",
-    # From fields
+    "CASCADE",
+    "NO_ACTION",
+    "RESTRICT",
+    "SET_NULL",
     "BigIntegerField",
     "BinaryField",
     "BooleanField",
+    "CheckConstraint",
+    "DatabaseConnectionMiddleware",
     "DateField",
     "DateTimeField",
     "DecimalField",
     "DurationField",
     "EmailField",
+    "F",
     "FloatField",
+    "ForeignKeyField",
     "GenericIPAddressField",
+    "Index",
     "IntegerField",
+    "JSONField",
+    "ManyToManyField",
+    "Model",
+    "Options",
     "PrimaryKeyField",
+    "Q",
+    "QuerySet",
     "RandomStringField",
+    "ReverseForeignKey",
+    "ReverseManyToMany",
     "SmallIntegerField",
+    "TextChoices",
     "TextField",
     "TimeField",
+    "TimeZoneField",
     "URLField",
     "UUIDField",
-    # From fields.json
-    "JSONField",
-    # From fields.timezones
-    "TimeZoneField",
-    # From indexes
-    "Index",
-    # From deletion
-    "CASCADE",
-    "NO_ACTION",
-    "RESTRICT",
-    "SET_NULL",
-    # From options
-    "Options",
-    # From query
-    "QuerySet",
-    # From query_utils
-    "Q",
-    # From expressions
-    "F",
-    # From base
-    "Model",
-    # From fields.related
-    "ForeignKeyField",
-    "ManyToManyField",
-    # From fields.reverse_descriptors
-    "ReverseForeignKey",
-    "ReverseManyToMany",
-    # From db
+    "UniqueConstraint",
     "get_connection",
-    "use_management_connection",
-    # From middleware
-    "DatabaseConnectionMiddleware",
-    # From registry
-    "register_model",
     "models_registry",
-    # Typed field imports
+    "register_model",
     "types",
+    "use_management_connection",
 ]

{plain_postgres-0.113.2 → plain_postgres-0.114.0}/plain/postgres/agents/.claude/rules/plain-postgres.md

@@ -23,7 +23,9 @@ can't infer the target type from the string — annotate explicitly so
 instance access keeps its type:
 
 ```python
-parent: TreeNode | None = types.ForeignKeyField("self", on_delete=postgres.CASCADE, allow_null=True)
+parent: TreeNode | None = types.ForeignKeyField(
+    "self", on_delete=postgres.CASCADE, allow_null=True
+)
 ```
 
 For `JSONField` and `EncryptedJSONField`, the stub returns `Any` (the