AnyDAC
ContentsIndexHome
PreviousUpNext
Common connection parameters

Describes the connection definition parameters common for all AnyDAC drivers.

Group
Links
Parameter 
Description 
Example value 
DriverID 
The AnyDAC base or virtual driver ID. 
MySQL 
MetaDefCatalog 
Specifies the default catalog for the application. The design time code will omit the catalog name in the object names, if it is equal to MetaDefCatalog. If MetaDefCatalog is '*', then catalog names will be omitted unconditionally. 
Northwind 
MetaDefSchema 
Specifies the default schema for the application. The design time code will omit the schema name in the object names if it is equal to MetaDefSchema. If MetaDefSchema is '*', then schema names will be omitted unconditionally. 
dbo 
MetaCurCatalog 
Specifies the current catalog for the application. If not specified, then its value will be received from the DBMS. When an application is asking for metadata and do not specify a catalog name, then AnyDAC will implicitly use the current catalog. If MetaCurCatalog is '*', then catalog names will be me omitted from the metadata parameters. 
MetaCurSchema 
Specifies the current schema for the application. If not specified, then its value will be received from the DBMS. When an application is asking for metadata and do not specify a schema name, then AnyDAC will implicitly use the current schema. If MetaCurSchema is '*', then schema names will be me omitted from the metadata parameters. 
MonitorBy 
Specifies the trace / monitor output for this connection definition. One of the following values may be specified:
  • FlatFile. The trace output will be put to a text file. To enable that, include TADMoniFlatFileClientLink into your application and set it Tracing property to True. AnyDAC will show the name of a trace file after an application is finished.
  • Remote. The trace output will be sent to the ADMonitor utility. As it may be used to monitor your application. To enable that, include TADMoniRemoteClientLink into your application and set it Tracing property to True. The ADMonitor must be run before connection will be established.
  • Custom. The trace output will be send to TADMoniCustomClientLink.OnOutput event handler. To enable that, include TADMoniCustomClientLink into your application and set it 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 
What do you think about this topic? Send feedback!