You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
One of my models has a property that is a Set. (Same problem with arrays.)
property:some_set,Object
When I create an instance, the set is properly saved. But when I try to update the set (add a field to the set, and save the instance) the new set is not saved to the database.
I wonder if a quick fix would be to add the ability to explicitly mark something as dirty? I think I could add this feature. It's not ideal, but I think it's doable.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
One of my models has a property that is a Set. (Same problem with arrays.)
When I create an instance, the set is properly saved. But when I try to update the set (add a field to the set, and save the instance) the new set is not saved to the database.
How to reproduce:
$ git clone https://github.com/js-coder/dm-sets.git $ cd dm-sets $ ruby set.rb $ ruby array.rb
The text was updated successfully, but these errors were encountered: