Click or drag to resize

IDataConfigurationProvider Interface

Defines a database configuration provider

Namespace:  SanteDB.Core.Configuration.Data
Assembly:  SanteDB.Core.Api (in SanteDB.Core.Api.dll) Version: 2.2.1
Syntax
public interface IDataConfigurationProvider : IReportProgressChanged

The IDataConfigurationProvider type exposes the following members.

Properties
  NameDescription
Public propertyDbProviderType
Get the database provider .NET type
Public propertyHostType
Gets the hosts on which this storage provider works
Public propertyInvariant
Gets the invariant name of the database solution this configuration provider configures
Public propertyName
Gets the name of the storage provider (for humans)
Public propertyOptionGroups
Gets the groupings for the options
Public propertyOptions
Get the configuration options
Public propertyPlatform
Gets the platforms on which this storage provider works
Top
Methods
  NameDescription
Public methodConfigure
Add the necessary information to the configuration file
Public methodCreateConnectionString
Creates the specified connection string with options
Public methodCreateDatabase
Create the specified database in the provider
Public methodDeploy Obsolete.
Deploy the specified data feature to the specified configuration option
Public methodGetDatabases
Get all databases from the remote server
Public methodGetFeatures Obsolete.
Get data features matching this invariant name
Public methodParseConnectionString
Parse the specified connection string into a dictionary of key/value pairs
Public methodTestConnectionString
Tests the specified connection string to ensure it is valid with the provider and the remote machine exists
Top
Events
  NameDescription
Public eventProgressChanged
Fired when the progress of this instance has changed
(Inherited from IReportProgressChanged.)
Top
Remarks
When running SanteDB iCDR or dCDR server, the configuration tooling uses implementations of these classes to fetch current databases, create new databases, reflect on connection properties, etc. Implementations of these classes should be tied directly to a particular plugin for a new database.
See Also