There’s a ticket for the ForeignKey migration issue he discusses: code.djangoproject.com/ticket/34417
The PR is half-written with review comments to address, if anyone would like to revive the code and finish it off!
The PR is half-written with review comments to address, if anyone would like to revive the code and finish it off!
#34417 (AlterField migration on ForeignKey field re-creates foreign key constraints unnecessarily)
– Django
code.djangoproject.com
October 12, 2025 at 9:48 PM
There’s a ticket for the ForeignKey migration issue he discusses: code.djangoproject.com/ticket/34417
The PR is half-written with review comments to address, if anyone would like to revive the code and finish it off!
The PR is half-written with review comments to address, if anyone would like to revive the code and finish it off!
The "art of programming" might feel like it's crumbling, yet I'm still trying to keep up with software engineering developments. I'm now almost a year into learning event sourcing. It's satisfying to be able to write clean code even for legacy codebases. Sample con raffle feature—real world Python!
![Screenshot of Python source code:
```
from datetime import datetime
from sqlalchemy import ForeignKey
from sqlalchemy.orm import Mapped, mapped_column, relationship
from database import Model
from reg.models import Event, Registration, db
from reg.villa_raffle.query import is_registration_entered_for_villa_raffle
from reg.villa_raffle.end import VillaRaffleEnded
from reg.villa_raffle.start import VillaRaffleStarted
from user.models import User
from furryest.utils import Failure
class VillaRaffleEntered(Model):
event_id: Mapped[int] = mapped_column(ForeignKey(Event.id), nullable=False)
registration_id: Mapped[int] = mapped_column(ForeignKey(Registration.id), nullable=False)
entered_at: Mapped[datetime] = mapped_column(nullable=False, defalt=datetime.now)
event: Mapped[Event] = relationship()
registration: Mapped[Registration] = relationship()
def enter_villa_raffle(user: User, registration: Registration, event: Event) -> VillaRaffleEntered | Failure:
if not db.session.query(VillaRaffleStarted).filter_by(event_id=event.id).first():
return Failure("Villa raffle has not been started for this event.")
elif db.session.query(VillaRaffleEnded).filter_by(event_id=event.id).first():
return Failure("Villa raffle has already ended for this event.")
elif registration.event_id != event.id:
return Failure("Registration does not belong to the given event.")
elif registration.user_id != user.id:
return Failure("Registration does not belong to the given user.")
elif is_registration_entered_for_villa_raffle(registration=registration, event=event):
return Failure("This registration has already entered the villa raffle.")
villa_raffle_entered = VillaRaffleEntered(
event_id=event.id,
registration_id=registration.id
)
villa_raffle_entered.save()
return villa_raffle_entered
```](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:l62vabhiophfeg3xbwm5jeku/bafkreibegqxosceazkyd2eequgasnfd65nvem3tp2crvel3zla77agqrmy)
March 28, 2026 at 7:59 PM
The "art of programming" might feel like it's crumbling, yet I'm still trying to keep up with software engineering developments. I'm now almost a year into learning event sourcing. It's satisfying to be able to write clean code even for legacy codebases. Sample con raffle feature—real world Python!
Django のForeignKey まわりがよくわからない
May 18, 2025 at 10:24 PM
Django のForeignKey まわりがよくわからない
When you're coding in Django, you'll likely need to connect pieces of data. This is where ForeignKey comes in - it helps you link one model to another. John teaches you how it works, how to access related objects, how to create foreign key relationships, & more.
www.freecodecamp.org/news/how-to-...
www.freecodecamp.org/news/how-to-...
April 23, 2025 at 12:01 AM
When you're coding in Django, you'll likely need to connect pieces of data. This is where ForeignKey comes in - it helps you link one model to another. John teaches you how it works, how to access related objects, how to create foreign key relationships, & more.
www.freecodecamp.org/news/how-to-...
www.freecodecamp.org/news/how-to-...
Django Fellow Report- Sarah
Sarah Boyce triaged and reviewed Django fixes covering Playwright testing, admin query parameters, annotation transforms, and GEOS 3.15 compatibility. She also documented the YYYY[.N] release-versioning scheme and #djangonews
forum.djangoproject.com/t/django-fe...
Sarah Boyce triaged and reviewed Django fixes covering Playwright testing, admin query parameters, annotation transforms, and GEOS 3.15 compatibility. She also documented the YYYY[.N] release-versioning scheme and #djangonews
forum.djangoproject.com/t/django-fe...
Django Fellow Report - Sarah - 2026
Week ending 2026-09-13 (Week 37) This week was quite admin heavy but all positive things! Triaged #37306 (Add --tracing and --video options to the Playwright test runner) – Django (accepted) #37337 (MigrationAutodetector defers ForeignKey components of CompositePrimaryKey to AddField, causing FieldDoesNotExist on CreateModel) – Django (worksforme) #37330 (Transform on an annotation alias crashes when output_field is not attached to a model) – Django (accepted) #37341 (Update "vast range" phras...
forum.djangoproject.com
September 23, 2026 at 10:00 PM
Django Fellow Report- Sarah
Sarah Boyce triaged and reviewed Django fixes covering Playwright testing, admin query parameters, annotation transforms, and GEOS 3.15 compatibility. She also documented the YYYY[.N] release-versioning scheme and #djangonews
forum.djangoproject.com/t/django-fe...
Sarah Boyce triaged and reviewed Django fixes covering Playwright testing, admin query parameters, annotation transforms, and GEOS 3.15 compatibility. She also documented the YYYY[.N] release-versioning scheme and #djangonews
forum.djangoproject.com/t/django-fe...
Foreign key fields now let you control referential integrity policies directly from the model definition.
Previously, Cot always generated RESTRICT for both policies. Now you can choose any standard option giving you full control over what happens when a referenced row is updated or deleted.
Previously, Cot always generated RESTRICT for both policies. Now you can choose any standard option giving you full control over what happens when a referenced row is updated or deleted.
![use cot::db::{ForeignKey, ForeignKeyOnDeletePolicy, ForeignKeyOnUpdatePolicy};
#[model]
struct Comment {
#[model(primary_key)]
id: Auto<i32>,
#[model(
on_delete = ForeignKeyOnDeletePolicy::Cascade,
on_update = ForeignKeyOnUpdatePolicy::Cascade,
)]
post: ForeignKey<Post>,
body: String,
}](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:pzelvzn4nvoafylnpiogys4d/bafkreihegpsmix2lphvvzktzifzop2cjzpfvuhyfaehw5h76xjbyxklwxi)
July 13, 2026 at 6:40 PM
Foreign key fields now let you control referential integrity policies directly from the model definition.
Previously, Cot always generated RESTRICT for both policies. Now you can choose any standard option giving you full control over what happens when a referenced row is updated or deleted.
Previously, Cot always generated RESTRICT for both policies. Now you can choose any standard option giving you full control over what happens when a referenced row is updated or deleted.
15five-django-ajax-selects - 1.5.2.155
Edit ForeignKey, ManyToManyField and CharField in Django Admin using jQuery UI AutoComplete.
Author: Chris Sattinger
Edit ForeignKey, ManyToManyField and CharField in Django Admin using jQuery UI AutoComplete.
Author: Chris Sattinger
August 6, 2024 at 10:00 PM
15five-django-ajax-selects - 1.5.2.155
Edit ForeignKey, ManyToManyField and CharField in Django Admin using jQuery UI AutoComplete.
Author: Chris Sattinger
Edit ForeignKey, ManyToManyField and CharField in Django Admin using jQuery UI AutoComplete.
Author: Chris Sattinger
Django 6.1 adds model field fetch modes that can reduce many N plus 1 query cases, database level ForeignKey delete options, and dictionary based email settings. It supports Python 3.12 through 3.14, so review upgrade notes first.
August 27, 2026 at 11:44 AM
Django 6.1 adds model field fetch modes that can reduce many N plus 1 query cases, database level ForeignKey delete options, and dictionary based email settings. It supports Python 3.12 through 3.14, so review upgrade notes first.
Django 6.1 adds model field fetch modes that can reduce many N plus 1 query cases, database level ForeignKey delete options, and dictionary based email settings. It supports Python 3.12 through 3.14, so review upgrade notes first.
August 27, 2026 at 9:14 AM
Django 6.1 adds model field fetch modes that can reduce many N plus 1 query cases, database level ForeignKey delete options, and dictionary based email settings. It supports Python 3.12 through 3.14, so review upgrade notes first.
Django 6.1 released
Django 6.1 is now available with features including model field fetch modes, database-level ForeignKey delete options, and dictionary-based email settings. Django 6.0 has ended mainstream support and will rec…
https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/
Django 6.1 is now available with features including model field fetch modes, database-level ForeignKey delete options, and dictionary-based email settings. Django 6.0 has ended mainstream support and will rec…
https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/
August 13, 2026 at 6:15 AM
Django 6.1 released
Django 6.1 is now available with features including model field fetch modes, database-level ForeignKey delete options, and dictionary-based email settings. Django 6.0 has ended mainstream support and will rec…
https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/
Django 6.1 is now available with features including model field fetch modes, database-level ForeignKey delete options, and dictionary-based email settings. Django 6.0 has ended mainstream support and will rec…
https://www.djangoproject.com/weblog/2026/aug/05/django-61-released/
Django 6.1 is out now!
New features include:
🐍Database level delete options for ForeignKey
🐍Dictionary based email settings
🐍Support for Python 3.12-3.14
🐍Model field fetch modes
and more!
New features include:
🐍Database level delete options for ForeignKey
🐍Dictionary based email settings
🐍Support for Python 3.12-3.14
🐍Model field fetch modes
and more!
August 7, 2026 at 12:56 PM
Django 6.1 is out now!
New features include:
🐍Database level delete options for ForeignKey
🐍Dictionary based email settings
🐍Support for Python 3.12-3.14
🐍Model field fetch modes
and more!
New features include:
🐍Database level delete options for ForeignKey
🐍Dictionary based email settings
🐍Support for Python 3.12-3.14
🐍Model field fetch modes
and more!
“Oh yeah the Flowery mmrs doesn’t work on recomp right now because I used stoi instead of stoll and one of the zsounds has DEADBEEF as its foreignKey”
Statements dreamt up by the utterly Deranged
Statements dreamt up by the utterly Deranged
July 6, 2026 at 6:10 PM
“Oh yeah the Flowery mmrs doesn’t work on recomp right now because I used stoi instead of stoll and one of the zsounds has DEADBEEF as its foreignKey”
Statements dreamt up by the utterly Deranged
Statements dreamt up by the utterly Deranged
About Default ForeignKey Value
www.djangotricks.com/tricks/3KUVg...
www.djangotricks.com/tricks/3KUVg...
About Default ForeignKey Value
www.djangotricks.com
December 5, 2025 at 6:39 PM
About Default ForeignKey Value
www.djangotricks.com/tricks/3KUVg...
www.djangotricks.com/tricks/3KUVg...
Connecting #Django admin inline object should be simpler for objects without direct foreignkey. Something like overriding a simple "get_queryset" 😒😒
April 10, 2025 at 5:43 PM
Connecting #Django admin inline object should be simpler for objects without direct foreignkey. Something like overriding a simple "get_queryset" 😒😒
SQLAlchemy applications can connect to Aurora DSQL by using UUID primary keys, defining relationships with explicit `primaryjoin` and `foreign()` annotations instead of `ForeignKey()` constraints, and configuring the engine in AUTOCOMMIT mode to avoid unsupported SAVEPOINT operations.
Building Python applications with SQLAlchemy and Aurora DSQL
SQLAlchemy applications can connect to Aurora DSQL by using UUID primary keys, defining relationships with explicit `primaryjoin` and `foreign()` annotations instead of `ForeignKey()` constraints, and configuring the engine in AUTOCOMMIT mode to avoid unsupported SAVEPOINT operations.
aws-news.com
June 8, 2026 at 8:12 PM
SQLAlchemy applications can connect to Aurora DSQL by using UUID primary keys, defining relationships with explicit `primaryjoin` and `foreign()` annotations instead of `ForeignKey()` constraints, and configuring the engine in AUTOCOMMIT mode to avoid unsupported SAVEPOINT operations.
Q: What sits between you and your Data? A: Identifiers! Read: #URI #LinkedData #PrimaryKey #ForeignKey #ODBC #NewSQL
November 21, 2024 at 8:03 AM
Q: What sits between you and your Data? A: Identifiers! Read: #URI #LinkedData #PrimaryKey #ForeignKey #ODBC #NewSQL
**INNER JOIN ON vs WHERE clause**
#Trending #CurrentEvents
Read the full story: stackoverflow.com/questions/10...
#Trending #CurrentEvents
Read the full story: stackoverflow.com/questions/10...
INNER JOIN ON vs WHERE clause
For simplicity, assume all relevant fields are NOT NULL.
You can do:
SELECT
table1.this, table2.that, table2.somethingelse
FROM
table1, table2
WHERE
table1.foreignkey = table2.primary...
stackoverflow.com
October 30, 2024 at 10:05 AM
**INNER JOIN ON vs WHERE clause**
#Trending #CurrentEvents
Read the full story: stackoverflow.com/questions/10...
#Trending #CurrentEvents
Read the full story: stackoverflow.com/questions/10...
sqlalchemy、ForeignKeyの指定の仕方がよくわかってない。joinはわかった。
June 1, 2024 at 11:49 AM
sqlalchemy、ForeignKeyの指定の仕方がよくわかってない。joinはわかった。
Project: django/django
File: tests/model_formsets/tests.py:1337
def test_unique_true_enforces_max_num_one(self): # ForeignKey with unique=True should enforce max_num=1
SVG: dark, light
File: tests/model_formsets/tests.py:1337
def test_unique_true_enforces_max_num_one(self): # ForeignKey with unique=True should enforce max_num=1
SVG: dark, light
August 30, 2025 at 10:36 PM
Project: django/django
File: tests/model_formsets/tests.py:1337
def test_unique_true_enforces_max_num_one(self): # ForeignKey with unique=True should enforce max_num=1
SVG: dark, light
File: tests/model_formsets/tests.py:1337
def test_unique_true_enforces_max_num_one(self): # ForeignKey with unique=True should enforce max_num=1
SVG: dark, light
INNER JOIN ON vs WHERE clause
INNER JOIN ON vs WHERE clause
For simplicity, assume all relevant fields are NOT NULL. You can do: SELECT table1.this, table2.that, table2.somethingelse FROM table1, table2 WHERE table1.foreignkey = table2.primary...
stackoverflow.com
October 30, 2024 at 1:07 PM
INNER JOIN ON vs WHERE clause
[Articles] Virtual Tables and Django Foreignkeys
Disabling default database constraints with db_constraint=False on ForeignKey and ManyToMany fields ensures Django unmanaged virtual tables operate correctly in SQLite temp schemas. #djangonews
paultraylor.net/blog/2025/v...
Disabling default database constraints with db_constraint=False on ForeignKey and ManyToMany fields ensures Django unmanaged virtual tables operate correctly in SQLite temp schemas. #djangonews
paultraylor.net/blog/2025/v...
Virtual Tables and Django Foreignkeys
I have been continuing with my virtual table implementation, though taking a short break to do some more integration on the Django side.
I have an ideas site that I use as a kind of wiki to keep track of various ideas.
# the default model I'm using from my virtual table integration class FrontmatterModel(models.Model): inode = models.PositiveIntegerField(primary_key=True, editable=False) path = models.FilePathField(unique=True, editable=False) slug = models.SlugField() content = models.TextField() excerpt = models.TextField(blank=True) metadata = models.JSONField() class Meta: abstract = True # Custom model for my idea object itself # These also exist in the `metadata` json frontmatter, but putting them here # makes them nicer to deal with from Django class Idea(FrontmatterModel): title = models.CharField(max_length=128) status = models.ForeignKey(Status, on_delete=models.SET_NULL, null=True, db_column="dir") homepage = models.URLField(blank=True) repository = models.URLField(blank=Tru
paultraylor.net
July 24, 2025 at 2:00 AM
[Articles] Virtual Tables and Django Foreignkeys
Disabling default database constraints with db_constraint=False on ForeignKey and ManyToMany fields ensures Django unmanaged virtual tables operate correctly in SQLite temp schemas. #djangonews
paultraylor.net/blog/2025/v...
Disabling default database constraints with db_constraint=False on ForeignKey and ManyToMany fields ensures Django unmanaged virtual tables operate correctly in SQLite temp schemas. #djangonews
paultraylor.net/blog/2025/v...