check for dirty indexes before add it to a collection#143
check for dirty indexes before add it to a collection#143angel9484 wants to merge 3 commits intonpgall:masterfrom
Conversation
When a collection with indexes is filled with data, you can have that indexes into separate variables or static fields. Then you could add this indexes to a new collection (p.ex the same collection but re-instantiated from a persistence serialization system), but this indexes can have data and can associate with the new collection silent and dirty. This checks that the index was used and is dirty and throws an exception to warn the user. Added new QueryOption DISABLE_DIRTY_CHECK_OPTION boolean that handles the deactivation of the newfeature/constraint. This check is enabled by default.
|
`public class Main { }` The output: |
|
`public class Main { }` The output: Process finished with exit code 1 |
a7fb59c to
1ed900c
Compare
New feature/Constraint:
When a collection with indexes is filled with data, you can have that indexes into separate variables or static fields.
Then you could add this indexes to a new collection (p.ex the same collection but re-instantiated from a persistence serialization system), but this indexes can have data and can associate with the new collection silent and dirty.
This checks that the index was used and is dirty and throws an exception to warn the user.
If you let this with the QueryOption you assume that you could have indexes with different data on multiple collections, or data into the index that could be changed into the collection after a de-serialization process
Added new QueryOption DISABLE_DIRTY_CHECK_OPTION boolean that handles the deactivation of the newfeature/constraint. This check is disabled by default.