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

Difference in persister behavior when handling array defaults #965

Open
dlpierce opened this issue Sep 9, 2024 · 0 comments
Open

Difference in persister behavior when handling array defaults #965

dlpierce opened this issue Sep 9, 2024 · 0 comments

Comments

@dlpierce
Copy link
Contributor

dlpierce commented Sep 9, 2024

While working on valkyrie/ferdora support in hyrax, I've discovered a difference in the way the various persisters handle the default value for an attribute of type array (a frozen empty array).

After persisting a new resource, or when reloading it, the postgres and memory persisters produce a resource with an unfrozen array, while the fedora and solr persisters the array is frozen. Based on past work in valkyrie, I believe the intention is for the default value for arrays to be frozen for all of the persistence adapters. See this branch which has a spec added for this case, but no failures for fedora and solr.

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

No branches or pull requests

1 participant