Skip to content

mapper should raise an error if PK columns do not match _instance_key #412

Closed
@sqlalchemy-bot

Description

@sqlalchemy-bot
Collaborator

Migrated issue, originally created by Michael Bayer (@zzzeek)

i dont think anyones sticking modified PK cols in the flush(), so i think this can probably have an explicit check.

Activity

sqlalchemy-bot

sqlalchemy-bot commented on Jan 12, 2007

@sqlalchemy-bot
CollaboratorAuthor

Michael Bayer (@zzzeek) wrote:

this was implemented in changeset:2186

sqlalchemy-bot

sqlalchemy-bot commented on Jan 12, 2007

@sqlalchemy-bot
CollaboratorAuthor

Changes by Michael Bayer (@zzzeek):

  • changed status to closed
added
blockerissue that must be resolved asap as it is preventing things from working
on Nov 27, 2018
added this to the 0.3.4 milestone on Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockerissue that must be resolved asap as it is preventing things from workingfeatureorm

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @sqlalchemy-bot

        Issue actions

          mapper should raise an error if PK columns do not match _instance_key · Issue #412 · sqlalchemy/sqlalchemy