Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
sqlalchemy-bot opened this issue Jan 4, 2007 · 2 comments
Closed

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

sqlalchemy-bot opened this issue Jan 4, 2007 · 2 comments
Labels
blocker issue that must be resolved asap as it is preventing things from working feature orm
Milestone
0.3.4

Comments

@sqlalchemy-bot
Copy link
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.
@sqlalchemy-bot
Copy link
Collaborator Author

Michael Bayer (@zzzeek) wrote:

this was implemented in changeset:2186

@sqlalchemy-bot
Copy link
Collaborator Author

Changes by Michael Bayer (@zzzeek):

  • changed status to closed

@sqlalchemy-bot sqlalchemy-bot added feature blocker issue that must be resolved asap as it is preventing things from working orm labels Nov 27, 2018
@sqlalchemy-bot sqlalchemy-bot added this to the 0.3.4 milestone Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocker issue that must be resolved asap as it is preventing things from working feature orm
Projects
None yet
Milestone
0.3.4
Development

No branches or pull requests
1 participant
@sqlalchemy-bot