Common Connection Parameters (FireDAC)

From Appmethod Topics
Jump to: navigation, search

Go Up to Database Connectivity (FireDAC)

The following table describes the connection definition parameters common to all FireDAC drivers.

Parameter Description Example value
DriverID The FireDAC base or virtual driver ID. MySQL
MetaDefCatalog Specifies the default catalog for the application. The design time code omits the catalog name in the object name if it is equal to MetaDefCatalog. If MetaDefCatalog is '*', then the catalog name is omitted unconditionally. Northwind
MetaDefSchema Specifies the default schema for the application. The design time code omits the schema name in the object name if it is equal to MetaDefSchema. If MetaDefSchema is '*', then the schema name is omitted unconditionally. dbo
MetaCurCatalog Specifies the current catalog for the application. If it is not specified, then its value is received from the DBMS. If an application asks for metadata and you do not specify a catalog name, then FireDAC implicitly uses the current catalog. If MetaCurCatalog is '*', then the catalog name is omitted from the metadata parameters. *
MetaCurSchema Specifies the current schema for the application. If it is not specified, then its value is received from the DBMS. If an application asks for metadata and you do not specify a schema name, then FireDAC implicitly uses the current schema. If MetaCurSchema is '*', then the schema name is omitted from the metadata parameters. *
MonitorBy Specifies the trace / monitor output for this connection definition. One of the following values can be specified:
  • FlatFile. The trace output is sent to a text file. To enable this, include TFDMoniFlatFileClientLink in your application and set its Tracing property to True. FireDAC shows the name of a trace file after an application is finished.
  • Remote. The trace output is sent to the FDMonitor utility in order to help you monitor your application. To enable this, include TFDMoniRemoteClientLink in your application and set its Tracing property to True. FDMonitor must be run before the connection is established.
  • Custom. The trace output is sent to the TFDMoniCustomClientLink.OnOutput event handler. To enable this, include TFDMoniCustomClientLink in your application and set its Tracing property to True.
FlatFile
Pooled Enables connection pooling for this connection definition. The default value is False. To use pooled connection, the connection definition must be persistent or private. True

See Also