Administrator
User Guide
Multiwrite Databases and Extracts
:
Using Extracts
: Flushing
Flushing
When an extract user makes changes and saves them, they are stored in the extract. The changes can then be
flushed
, which means that they will be made available to the parent extract.
The local changes are copied to the parent extract, but the elements are not released. Users who have access to the parent database can now see the changes, but they still cannot make changes of their own to the elements.
A single element, or a database, or a collection of elements can be flushed.
If changes need to be made available in the master database, it will be necessary to flush the changes up through each level of extracts. Users accessing extracts in other branches of the extract tree will need to
refresh
their views of the data to see the changes.
The following diagram illustrates the sequence of commands that need to be given so that a user working on extract B2 will be able to see the changes made by a user working on extract A2.
A flush can, optionally, do an implied refresh. It is more efficient to do this.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.