Special Relationship Persistence Patterns

    • A table contains a foreign key to itself, and a single row will have a foreign key value pointing to its own primary key.

    • Two tables each contain a foreign key referencing the other table, with a row in each table referencing the other.

    For example:

    Or:

    2. -------------------------------------------             ---------------------------------
    3. widget_id     name        favorite_entry_id             entry_id      name      widget_id
    4.    1       'somewidget'          5                         5       'someentry'     1

    In the first case, a row points to itself. Technically, a database that uses sequences such as PostgreSQL or Oracle can INSERT the row at once using a previously generated value, but databases which rely upon autoincrement-style primary key identifiers cannot. The always assumes a “parent/child” model of row population during flush, so unless you are populating the primary key/foreign key columns directly, relationship() needs to use two statements.

    In the second case, the “widget” row must be inserted before any referring “entry” rows, but then the “favorite_entry_id” column of that “widget” row cannot be set until the “entry” rows have been generated. In this case, it’s typically impossible to insert the “widget” and “entry” rows using just two INSERT statements; an UPDATE must be performed in order to keep foreign key constraints fulfilled. The exception is if the foreign keys are configured as “deferred until commit” (a feature some databases support) and if the identifiers were populated manually (again essentially bypassing ).

    To enable the usage of a supplementary UPDATE statement, we use the relationship.post_update option of . This specifies that the linkage between the two rows should be created using an UPDATE statement after both rows have been INSERTED; it also causes the rows to be de-associated with each other via UPDATE before a DELETE is emitted. The flag should be placed on just one of the relationships, preferably the many-to-one side. Below we illustrate a complete example, including two ForeignKey constructs:

    1. >>> w1 = Widget(name="somewidget")
    2. >>> e1 = Entry(name="someentry")
    3. >>> w1.favorite_entry = e1
    4. >>> w1.entries = [e1]
    5. >>> session.add_all([w1, e1])
    6. BEGIN (implicit)
    7. INSERT INTO widget (favorite_entry_id, name) VALUES (?, ?)
    8. (None, 'somewidget')
    9. INSERT INTO entry (widget_id, name) VALUES (?, ?)
    10. (1, 'someentry')
    11. UPDATE widget SET favorite_entry_id=? WHERE widget.widget_id = ?
    12. (1, 1)
    13. COMMIT

    An additional configuration we can specify is to supply a more comprehensive foreign key constraint on Widget, such that it’s guaranteed that favorite_entry_id refers to an that also refers to this Widget. We can use a composite foreign key, as illustrated below:

    The above mapping features a composite bridging the widget_id and favorite_entry_id columns. To ensure that Widget.widget_id remains an “autoincrementing” column we specify Column.autoincrement to the value "ignore_fk" on , and additionally on each relationship() we must limit those columns considered as part of the foreign key for the purposes of joining and cross-population.

    Mutable Primary Keys / Update Cascades

    When the primary key of an entity changes, related items which reference the primary key must also be updated as well. For databases which enforce referential integrity, the best strategy is to use the database’s ON UPDATE CASCADE functionality in order to propagate primary key changes to referenced foreign keys - the values cannot be out of sync for any moment unless the constraints are marked as “deferrable”, that is, not enforced until the transaction completes.

    It is highly recommended that an application which seeks to employ natural primary keys with mutable values to use the ON UPDATE CASCADE capabilities of the database. An example mapping which illustrates this is:

    1. class User(Base):
    2.     __tablename__ = "user"
    3.     __table_args__ = {"mysql_engine": "InnoDB"}
    5.     username = mapped_column(String(50), primary_key=True)
    6.     fullname = mapped_column(String(100))
    7.     addresses = relationship("Address")
    10. class Address(Base):
    11.     __tablename__ = "address"
    12.     __table_args__ = {"mysql_engine": "InnoDB"}
    14.     email = mapped_column(String(50), primary_key=True)
    15.     username = mapped_column(
    16.         String(50), ForeignKey("user.username", onupdate="cascade")
    17.     )

    Above, we illustrate onupdate="cascade" on the ForeignKey object, and we also illustrate the mysql_engine='InnoDB' setting which, on a MySQL backend, ensures that the InnoDB engine supporting referential integrity is used. When using SQLite, referential integrity should be enabled, using the configuration described at .

    See also

    Using foreign key ON DELETE cascade with ORM relationships - supporting ON DELETE CASCADE with relationships

    In those cases when a database that does not support referential integrity is used, and natural primary keys with mutable values are in play, SQLAlchemy offers a feature in order to allow propagation of primary key values to already-referenced foreign keys to a limited extent, by emitting an UPDATE statement against foreign key columns that immediately reference a primary key column whose value has changed. The primary platforms without referential integrity features are MySQL when the MyISAM storage engine is used, and SQLite when the PRAGMA foreign_keys=ON pragma is not used. The Oracle database also has no support for ON UPDATE CASCADE, but because it still enforces referential integrity, needs constraints to be marked as deferrable so that SQLAlchemy can emit UPDATE statements.

    The feature is enabled by setting the relationship.passive_updates flag to False, most preferably on a one-to-many or many-to-many . When “updates” are no longer “passive” this indicates that SQLAlchemy will issue UPDATE statements individually for objects referenced in the collection referred to by the parent object with a changing primary key value. This also implies that collections will be fully loaded into memory if not already locally present.

    Our previous mapping using passive_updates=False looks like:

    Key limitations of passive_updates=False include:

    • it performs much more poorly than direct database ON UPDATE CASCADE, because it needs to fully pre-load affected collections using SELECT and also must emit UPDATE statements against those values, which it will attempt to run in “batches” but still runs on a per-row basis at the DBAPI level.

    • the feature cannot “cascade” more than one level. That is, if mapping X has a foreign key which refers to the primary key of mapping Y, but then mapping Y’s primary key is itself a foreign key to mapping Z, passive_updates=False cannot cascade a change in primary key value from Z to X.

    • Configuring passive_updates=False only on the many-to-one side of a relationship will not have a full effect, as the unit of work searches only through the current identity map for objects that may be referencing the one with a mutating primary key, not throughout the database.