IDbCollationProperties.GetCollationProperties Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Returns the collation properties used for a connection.
public:
bool GetCollationProperties([Runtime::InteropServices::Out] System::String ^ % cultureName, [Runtime::InteropServices::Out] bool % caseSensitive, [Runtime::InteropServices::Out] bool % accentSensitive, [Runtime::InteropServices::Out] bool % kanatypeSensitive, [Runtime::InteropServices::Out] bool % widthSensitive);
public bool GetCollationProperties (out string cultureName, out bool caseSensitive, out bool accentSensitive, out bool kanatypeSensitive, out bool widthSensitive);
abstract member GetCollationProperties : string * bool * bool * bool * bool -> bool
Public Function GetCollationProperties (ByRef cultureName As String, ByRef caseSensitive As Boolean, ByRef accentSensitive As Boolean, ByRef kanatypeSensitive As Boolean, ByRef widthSensitive As Boolean) As Boolean
Parameters
- cultureName
- String
The name of the culture to use for collation.
- caseSensitive
- Boolean
Indicates that the collation should be case sensitive.
- accentSensitive
- Boolean
Indicates that the collation should be accent sensitive.
- kanatypeSensitive
- Boolean
Indicates that the collation should be kana type sensitive.
- widthSensitive
- Boolean
Indicates that the collation should be width sensitive.
Returns
Returns true if the collation properties could be detected for the current connection.
Remarks
This method returns the collation properties used for a connection. These property values can be used in reports which request auto-detected collation properties.
A data processing extension needs to execute one or more queries against a data source in order to determine the default collation properties. In order to execute queries from within the data extension, transactions need to be taken into account. For some managed data providers, the transaction property on a command must be explicitly set if the connection is in a transaction, even if the command was created using CreateCommand. To do this, you must cache the transaction when BeginTransaction is called, and release the transaction on Commit or Rollback.