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.

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

as_of() and m2m fields - response gives non_historic values #1257

Open
baranma75 opened this issue Sep 15, 2023 · 4 comments
Open

as_of() and m2m fields - response gives non_historic values #1257

baranma75 opened this issue Sep 15, 2023 · 4 comments
Labels
bug Issues related to confirmed bugs

Comments

@baranma75
Copy link

as_of() and m2m fields

receives in response the current non-history values for the m2m fields, how is it right to use as_of() with m2m fields?

@ddabble
Copy link
Member

ddabble commented Sep 15, 2023

I'm fairly sure this is a bug with the same cause as #1063 - which seems to be that each history record's instance property doesn't provide any related managers for the historical values of the M2M fields.

I started working on a fix around the time that issue was opened, but haven't gotten around to finish it yet, unfortunately.

@ddabble ddabble added the bug Issues related to confirmed bugs label Sep 15, 2023
@baranma75
Copy link
Author

I will temporarily query the historical database with a separate query. Thanks.

@frossigneux
Copy link

Hello,
I have the same problem. @ddabble is there a fix or a workaround?
Thanks

@baranma75
Copy link
Author

Hi,

I read by separate query from historictables and add/replace in result

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues related to confirmed bugs
Projects
None yet
Development

No branches or pull requests

3 participants