Data.DBXCommon.TDBXPropertyNames
Delphi
TDBXPropertyNames = class
C++
class PASCALIMPLEMENTATION TDBXPropertyNames : public System::TObject
Properties
Type | Visibility | Source | Unit | Parent |
---|---|---|---|---|
class | public | Data.DBXCommon.pas Data.DBXCommon.hpp |
Data.DBXCommon | Data.DBXCommon |
Description
Property names for connections and drivers to provide information, such as user names and passwords.
The following table describes existing property names:
Constant | Description |
---|---|
|
If |
|
Buffer size in kilobytes to use for client driver transport read and write operations. Currently used by Data.DBXClient. |
|
Specifies the IP version for communications. |
|
Specifies the communication protocol. |
|
Specifies the maximum time to wait for a data packet to be exchanged. When the specified time expires, an exception is thrown. Not all drivers support this operation. |
|
Name of connection. If connection properties are read from the dbxconnections.ini file, this is the ini file section name. AdoDbx Client can use this property setting for a simple one property connection string. Connection names can also be used to load a connection from a TDBXConnectionFactory instance. |
|
String that provides the information required to establish the connection. |
|
Maximum time, in seconds, to wait for a new connection to be opened. If the specified time expires, an exception is thrown. Not all drivers support this operation. |
|
Name of a database to connect to. |
|
Specifies a key for a URL path toward DataSnap HTTP service. |
|
Host name of the machine that hosts the database. |
|
Delegate connection used by this connection. Delegate connections implement the dbExpress 4 driver framework. They can perform pre- or post-processing of all public and protected methods before delegating to the real connection or another delegate connection. |
|
Indicates that this driver is a delegate and can only be used in conjunction with a nondelegate driver. |
|
Display name of the driver. |
|
Used to load a managed driver dynamically.
|
|
Managed Driver loader class used to load a managed driver dynamically from an assembly. Comma-separated class and package name. |
|
Unique name for a dbExpress driver. Used by the dbxconnections.ini file to refer to a connections driver in the dbxdrivers.ini file. |
|
Used to load a native driver dynamically.
|
|
Native Driver loader class used to load a native driver dynamically from a package. Comma-separated class and package name. |
|
Used to provide an informative error message when driver cannot be loaded. |
|
Specifies a password required for a DataSnap user to authenticate with the server. |
|
Specifies the URL scheme to use to connect to the DataSnap server for authentication. |
|
Specifies the user name that is recognized by the DataSnap server. This is a different concept than a database user that is used for creating a database connection. |
|
Specifies the host name of the proxy server used to connect to the DataSnap server. |
|
Specifies the password of |
|
Specifies the port of the proxy server used to connect to the DataSnap server. |
|
Specifies the user name that is recognized by the proxy server used to connect to the DataSnap server. |
|
For internal use only. |
|
Specifies the filtering configuration. The filtering configuration is specified as a string containing data in JSON format. The filtering configuration must be a JSON object with key-value pairs that indicate which filters are used, and the configuration of those. The following JSON object shows how to use all supported filters and specify all their configuration properties: {
"PC1": {
"Key": "<PC1 key>"
},
"RSA": {
"KeyExponent": "<key exponent>",
"KeyLength": "<key length>",
"UseGlobalKey": "<false or true>"
},
"ZLibCompression": {
}
}
For example, to configure the ZLib compression filter, use the following value: { "ZLibCompression": {} }
|
|
Used by DBXDynalink drivers to specify the exported entry point for loading a driver prior to dbExpress 4. |
|
Host name of a database server that a driver connects to. |
|
dbxdrivers.ini section that specifies which drivers are enabled. |
|
ID of the IP implementation. |
|
Initial transaction isolation to use when connecting to a database. Transaction isolation can also be specified when a transaction is started. |
|
Used by DBXDynalink drivers to specify the name of the DBXDynalink DLL. |
|
Used by DBXDynalink drivers to specify the name of the DBXDynalink dylib for OS X. |
|
Maximum BLOB size. Set to –1 to specify no limit. |
|
Managed MetaData loader class used to load a managed driver dynamically from an assembly. |
|
Native MetaData loader class used to load a native driver dynamically from a package. |
|
Login password name used to connect to a database. |
|
Port number of a database server that a driver connects to. |
|
Provides the product name for the dbExpress metadata. |
|
Can be specified as a driver property as an override of the TDBXConnection.ProductVersion property. This may be necessary for drivers that do not have the ability to report the product version. The ProductVersion is a number in the format nn.nn.nnnn. |
|
Login role used to connect to a database. |
|
Size of the row set. |
|
Most applications should not need to use this constant. It is provided for backwards compatibility of the dbExpress VCL. VCL components use this setting to scope metadata requests. This property should be set to user-name.override-schema-name. For example, tables created by the MSSQL sa user are placed in the dbo schema. In this case, SchemaOverride can be set to 'sa.dbo'. This causes VCL to specify the 'dbo' schema for metadata requests when a connection is made using the 'sa' user. An SQL |
|
When connecting to a DataSnap server, this is the name of a server method that returns an instance of a TDBXConnection. All SQL statements and SQL stored procedure commands are executed against this TDBXConnection instance. This allows client and server methods to share the same database connection. There is a built-in DSAdmin.GetConnection method that takes a single input parameter, which is the name of a connection in the server-side |
|
This can be passed to the TDBXConnection.GetVendorProperty method to determine whether the driver supports parameter metadata. If parameter metadata is supported, executing the TDBXCommand.Prepare method causes the TDBXCommand parameter list to be automatically populated with parameters for the command. Note that if parameters were already added to the command, parameters are not automatically added. |
|
Specifies the path to a DataSnap server web application. For example, you can use URLPath to specify the virtual directory of a DataSnap server ISAPI dll. |
|
Login user name used to connect to a database. |
|
Used by DBXDynalink drivers. Name of a vendor-specific client library. |
|
Used by DBXDynalink drivers. Name of a vendor-specific client library for OS X. |
|
Used by DBXDynalink drivers. Name of a vendor-specific client library for 64-bit Windows. |