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

list and set operations applied even if object is invalid #2

Closed
fictorial opened this issue Dec 5, 2009 · 1 comment
Closed

list and set operations applied even if object is invalid #2

fictorial opened this issue Dec 5, 2009 · 1 comment

Comments

@fictorial
Copy link

I noticed that list and set operations are effectively committed immediately.

Consider the case where an object has a list that is updated with a "push", then an attribute is updated some invalid value, and the user tries to save the object. The validation fails yet the list is still left updated.
@soveran
Copy link
Owner

soveran commented Dec 10, 2009

Thanks for the observation. It is by design, the documentation has been updated accordingly.

cyx pushed a commit that referenced this issue Mar 7, 2012
Implement #2 and #3 as discussed with soveran.
85fc7f3 
Where #2 is the ability to index enumerables, and #3 is
the ability to index / add a unique for a virtual field.
This issue was closed.
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
@soveran @fictorial