Skip to content
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

Add support for HistoricOneToOneField #1389

Open
JordanHyatt opened this issue Sep 11, 2024 · 1 comment
Open

Add support for HistoricOneToOneField #1389

JordanHyatt opened this issue Sep 11, 2024 · 1 comment

Comments

@JordanHyatt
Copy link

HistoricForeignKey is a very nice feature, it would be great to extend this support to OneToOneFields.
@kgeidel
Copy link

kgeidel commented Sep 11, 2024

Yes, that would be swell. HistoricForeignKey(unique=True) throws that warning about using one to one. Would be nice to be able to have history on the 1-1 w/o needing to suppress that warning.

This was referenced Sep 16, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JordanHyatt @kgeidel