Get database parameter and SET DATABASE PARAMETER

Home

4D v15



	Get database parameter ( {aTable ;} selector {; stringValue} ) -> Function result SET DATABASE PARAMETER ( {aTable ;} selector ; value )

Description

A new selector parameter is available for the Get database parameter and SET DATABASE PARAMETER commands:

Constant	Type	Value
Circular log limitation	Longint	90

Scope: 4D local, 4D Server.
Kept between two sessions: No
Description: Maximum number of files to keep in rotation for each type of log. By default, all files are kept. If you pass a value X, only the X most recent files are kept, with the oldest being erased automatically when a new one is created. This setting applies to each of the following log files: request logs (selectors 28 and 45), debug log (selector 34), events log (selector 79), as well as Web request logs and Web debug logs (selectors 29 and 84 of the WEB SET OPTION command).
Possible values: Any integer value, 0 = keep all logs
Default value: 0 (no limitation)

Description

Originally introduced in 4D v14 R3

A new selector parameter is available for the Get database parameter and SET DATABASE PARAMETER commands:

Constant	Type	Value
SQL Server Port ID	Longint	88

Scope: 4D in local mode and 4D Server.
Kept between two sessions: Yes
Description: Sets or gets the number of the TCP port used by the 4D built-in SQL server with 4D in local mode and 4D Server. By default, the value is 19812. The TCP port number can be also set on the "SQL" page of the Database Settings dialog box. When this selector is used, the database setting is updated accordingly and will be kept after closing and restarting.
Possible values: 0 to 65535.
Default value: 19812

Description

Originally introduced in 4D v14 R5

A new selector parameter is available for the Get database parameter and SET DATABASE PARAMETER commands:

Constant	Type	Value
Use legacy network layer	Longint	87

Scope: 4D in local mode and 4D Server.
Kept between two sessions: Yes
Description: Sets or gets the current status of the legacy network layer for client/server connections. The legacy network layer is deprecated beginning with 4D v14 R5 and should be replaced progressively in your applications with the ServerNet network layer. ServerNet will be required in upcoming 4D releases in order to benefit from future network evolutions. For compatibility reasons, the legacy network layer is still supported to allow a smooth transition for existing applications; (it is used by default in applications converted from a release prior to v14 R5). Pass 1 in this parameter to use the legacy network layer (and disable ServerNet) for your client/server connections, and pass 0 to disable the legacy network (and use the ServerNet).
This property can also be set by means of the "Use legacy network layer" option found on the "Compatibility" page of the Database Settings (see New ServerNet Network Layer). In this section, you will also find a discussion about migration strategy. We recommend that you activate the ServerNet as soon as possible.
You will need to restart the application in order for this parameter to be taken into account. It is not available in the 64-bit version of 4D Server for OS X, which only supports the ServetNet; (it always returns 0).
Possible values: 0 or 1 (0 = do not use legacy layer, 1 = use legacy layer)
Default value: 0 in databases created with 4D v14 R5 or higher, 1 in databases converted from 4D v14 R4 or earlier.