CoreandServices.book - Ocean - Schlumberger

Data Management
The following code is a simple example of the use of the IDataSourceManager.
// Get the product family installed DataSourceManager
IDataSourceManager dsm = DataManager.DataSourceManager;
// Get the registered DataSources
ReadOnlyCollection sources = dsm.Sources;
// Add a new source, MockDataSource is defined earlier
MockDataSource mds = new MockDataSource(“MyMockSource”);
//MockDataSource defined earlier
dsm.AddSource(mds);
// Get the data source
IDataSource dataSource = dsm.GetSource(“MyMockSource”);
// Remove the data source
dsm.RemoveSource(dataSource);
Transactions
Transactions are required when data is being created, updated, or deleted. Transactions
make changes to data more efficient by grouping them so that fewer events are received.
For example, if you modify the values of data in a well log without a transaction, then you
will receive an event for each log sample you change. If each event causes the log to be
redrawn in your window, then your performance will suffer due to the repeated refreshing
of the window. However, if you enclose the code that updates the log samples in a
transaction, then only one event will be received at the end of all the log sample changes
when the transaction is committed. Ocean Petrel will not permit the modification of an
internally hosted domain object outside a transaction and will throw an exception if it is
attempted.
Working with transactions requires a few simple steps. These include:
1 Creating the transaction
2 Locking the appropriate data
3 Modifying the data
4 Committing the transaction (may mean different things depending on the data
persistence mechanism)
Schlumberger Private
Ocean Core 3-59