The General Release of PSQL v13 SP2, version 13.20, included new features and changes covered in the following topics:

This document may be updated after the release. Download the latest version at the Actian website.

PSQL v13 SP2 supports the following new platforms and editions:

The butil options -cache and -purge now apply to the local client cache of a Workgroup Engine. Previously, the command applied to the cache on a remote engine if a file on that system was the one specified in the command. Client cache must be enabled on the Workgroup Engine.

In the previous release, the Client Reporting Engine responded to SQL connections from remote systems running PSQL clients. In this release, the engine accepts only local connections.

In this release, PSQL automatically handles differences between the default encoding of the Client Reporting Engine and that of the PSQL Server configured as the storage server. Previously, if a PSQL Server database used the default setting for its code page, meaning the operating system code page, then the operating system where Client Reporting Engine was installed had to use that same code page for query results to display record data properly.

As a consequence, in addition to Windows installations of PSQL Server, you can now configure PSQL Server on Linux as a storage server for PSQL Client Reporting Engine on Windows systems. The Client Reporting Engine itself remains supported only on Windows.

In Btrieve operations, the length of the AUTOINC data type can now be 8 bytes as well as 2 or 4 bytes. The new length is available in files using 9.5 format and later. Btrieve files using the new 8-byte AUTOINC segment cannot be opened by engines from earlier releases.

In Btrieve 2 for PSQL v13 SP2, the CursorPosition type has been widened from integer to long long. Applications using the Btrieve 2 API in previous releases need to be recompiled for use with the new release.

In addition, the methods RecordRetrieveChunk, RecordAppendChunk, and RecordUpdateChunk are no longer limited to chunk lengths of Btrieve::MAXIMUM_RECORD_LENGTH. The removal of this restriction also applies to the related C and SWIG-generated functions. The change is backward compatible and does not require recompilation of previously implemented code.

Btrieve 2 adds the ability for Btrieve queries to use the LIKE operator in bulk operations to pattern-match data. The new feature operates on character-based data.

PSQL PDAC now supports RAD Studio 10.2 and Delphi 10.2.

The new functions TRY_CAST and TRY_CONVERT have been added in this release. TRY_CAST and TRY_CONVERT are identical to CAST and CONVERT except for handling of data values that cannot be converted. For CAST and CONVERT the entire query fails, but for TRY_CAST and TRY_CONVERT the columns in the query result that fail are returned as NULL.

You can now use a remote PowerShell session to verify that the PSQL engine is running and to stop and start it. See Verifying That the Database Engine is Running from a Remote PowerShell Session in PSQL User’s Guide.