| 
            
              AdapterBaseParseOutputMeasurementKeys Method
             | 
          
        
        
            Parses output measurement keys from connection string setting.
            
        
        Namespace: GSF.TimeSeries.AdaptersAssembly: GSF.TimeSeries (in GSF.TimeSeries.dll) Version: 2.4.258-beta
Syntaxpublic static MeasurementKey[] ParseOutputMeasurementKeys(
	DataSet dataSource,
	bool allowSelect,
	string value,
	string measurementTable = "ActiveMeasurements"
)
Public Shared Function ParseOutputMeasurementKeys ( 
	dataSource As DataSet,
	allowSelect As Boolean,
	value As String,
	Optional measurementTable As String = "ActiveMeasurements"
) As MeasurementKey()
public:
static array<MeasurementKey^>^ ParseOutputMeasurementKeys(
	DataSet^ dataSource, 
	bool allowSelect, 
	String^ value, 
	String^ measurementTable = L"ActiveMeasurements"
)
static member ParseOutputMeasurementKeys : 
        dataSource : DataSet * 
        allowSelect : bool * 
        value : string * 
        ?measurementTable : string 
(* Defaults:
        let _measurementTable = defaultArg measurementTable "ActiveMeasurements"
*)
-> MeasurementKey[] GSF.TimeSeries.Adapters.AdapterBase.ParseOutputMeasurementKeys = function(dataSource, allowSelect, value, measurementTable);
 View SourceParameters
- dataSource  DataSet
 - The DataSet used to define output measurements.
 - allowSelect  Boolean
 - Determines if database access via "SELECT" statement should be allowed for defining output measurement keys (see remarks about security).
 - value  String
 - Value of setting used to define output measurements, typically "outputMeasurements".
 - measurementTable  String  (Optional)
 - Measurement table name used to load additional meta-data; this is not used when specifying a FILTER expression.
 
Return Value
MeasurementKeyUser selected output measurements.
Remarks
            Security warning: allowing SELECT statements, i.e., setting allowSelect to true, should only be allowed in cases where SQL
            injection would not be an issue (e.g., in places where a user can already access the database and would have nothing to gain via an injection attack).
            
See Also