If the custom dataset uses its own background threads to manage a collection of cached features, the threads must use the Guard class to lock the dataset before modifying any features, and then call this method. Both operations should be done under the same Guard.

You can also call this method directly from the query method in the dataset. At that time, the dataset is already locked, you should not use a Guard in this case.

More information about thread safety of objects in a dataset can be found in Threading model, custom objects.

If the custom dataset uses its own background threads to manage a collection of cached features, the threads must use the Guard class to lock the dataset before modifying any features, and then call this method. Both operations should be done under the same Guard.

You can also call this method directly from the query method in the dataset. At that time, the dataset is already locked, you should not use a Guard in this case.

More information about thread safety of objects in a dataset can be found in Threading model, custom objects.

If the custom dataset uses its own background threads to manage a collection of cached features, the threads must use the Guard class to lock the dataset before modifying any features, and then call this method. Both operations should be done under the same Guard.

You can also call this method directly from the query method in the dataset. At that time, the dataset is already locked, you should not use a Guard in this case.

More information about thread safety of objects in a dataset can be found in Threading model, custom objects.