-
It's not clear to me why when initialValues re-seed matches the current state is dirty still true if it matches the reseeding. So even though we keepDirtyValues, if dirty values matches the reseed of…
-
### RE: Dirty Tracking
I have a great big Reform Form that creates/updates a product that is composed of a number models. The form gathers dimensions for the different components that all change siz…
-
Hi,
I would like to know whether dirty tracking will be part of the library?
Thanks,
Owen
-
Something like this?
``` ruby
user = User.new value: 1
user.attributes.changed? #=> nil
user.value = 2
user.attributes.changed? #=> {value: 2}
user.attributes.changed?(:value) #=> true
```
-
-
I noticed that the dirty tracking "is to be documented" in the readme. I played around with it and noticed to my surprise that changes are not wiped after a successful `save`/`save!` is it intentional…
-
Hi,
Is there a way to disable the dirty tracking functionality? This has been causing a lot of problems for us where documents with nested data structures aren't being saved because it doesn't think …
-
The dirty tracking API could be made much more useful with some additional methods being provided. Taking from Sequel:
`#column_changes`
`{name: ['old', 'new']}`
`#initial_value(column)`
`'old…
-
So far, POJOs aren't capable of dirty tracking. They just represent detached data. When storing POJOs back to the database, jOOQ doesn't know if any values have been changed, and thus just updates all…
-