Tracking Number

Description

PSQL-6620

System Error 612.0.-1 may be generated in PVSW.LOG when accessing files on a 4K sector disk.

PSQL-7166

Possible engine crash on Raspbian due to unaligned memory access fault.

PSQL-7217

FLOOR/CEILING scalar functions return incorrect values for very large positive/negative numbers, such as 63481882199254500.001

PSQL-7256

SELECT INTO should translate an IDENTITY column into the corresponding integer column since SELECT INTO does not create constraints or indexes.

PSQL-7314

Possible incorrect results from the DATEDIFF() scalar function when extracting milliseconds.

PSQL-7356

Possible crash when inserting into a view that is defined based on another view.

PSQL-7363

SQLGetTypeInfo with SQL_ALL_TYPES return redundant rows with on date/time/timestamp on odbc version 3.x

PSQL-7370

“Datasource Name Not Found” error returned to 64-bit PDAC application running on a client.

PSQL-7462

Dbo.fSQLStatistics() is returning an extra null row.

PSQL-7504

“Incompatible Types” may be returned when adding/subtracting TIMESTAMP or DATETIME values.

 Tracking Number

Description

N/A

Added support for Windows Server 2019 and Windows 10 October 2018 Update.

PSQL-3705

MKDE Tracing operations list does not include Stat Extended (65)

PSQL-4451

“General Parser Error” may be returned when creating a stored procedure that specifies a cursor for update that includes an ORDER BY.

PSQL-5113

Status 7011 is returned when creating a database pointing to existing DDFs with security enabled if you have the “Create dictionary files if they don’t exist” option checked.

PSQL-6162

Slow response when viewing table properties in PCC when the database is very large and the column names contain wildcard (%, _) or escape (\) characters.

PSQL-6251

In some environments, it can take a long time to establish a JDBC/ODBC connection.

PSQL-6283

ALTER TABLE is leaving temporary file handles open.

PSQL-6346

Rebuild utility should return status 30 for non-Btrieve files.

PSQL-6384

“Return statements in a UDF must have an argument” is generated when @@IDENTITY is the return value for a user defined function that returns an INTEGER .

PSQL-6386

“Error in Row” may be returned when a temporary sort file larger than 4GB is generated.

PSQL-6395

Possible SQL engine crash if a create index is specified for segments with a total length >255 and the last segment is a TIME column.

PSQL-6396

Possible SQL engine crash when creating a table with an IDENTITY column and specifying a negative default value (only 0 is allowed).

PSQL-6440

“Memory allocation error” may occur on a query with many AND/OR clauses that match an index with many segments.

PSQL-6452

Possible Syntax Error from a Stored Procedure using a DELETE statement.

PSQL-6468

ADO.NET provider returns an Invalid Cast Exception when calling a Stored Procedure defined with an OUT parameter of type UniqueIdentifier.

PSQL-6469

ADO.NET provider returns brackets instead of double quotes in the QuoteIdentifier() call.

PSQL-6492

Queries with LIKE run much slower in a non-English code page environment.

PSQL-6543

SQL Engine error messages may appear garbled in a Japanese environment.

PSQL-6545

A stored procedure created with a SIGNAL message on a Japanese OS may return a garbled message when the signal is encountered.

PSQL-6560

Query in a nested stored procedures using LOWER() on a column with UPPER.ALT may not return the correct results.

PSQL-6569

SQL_FETCH_BOOKMARK may return incorrect results from a SQL_SCROLLABLE results set on a forward-only cursor.

PSQL-6571

Application name in PSQL Monitor shows as “Unknown Application” for ADO.NET connections.

PSQL-6574

PCC takes a long time to open a 13.30 table with more than 4.2 billion rows.

PSQL-6589

Application crash when calling BeginTransaction and passing NULL for the DataBufferLength.

PSQL-6615

NULLIF() scalar function may return incorrect results when used with a wide column.

PSQL-6616

PCC Add row should allow a negative value for Identity columns.

PSQL-6627

Possible incorrect results from query with a subquery restrictions combined with other restrictions.

PSQL-6648

Removed dependence on MS function for lead-byte checking in double-byte data.

PSQL-6651

Status 170 when rolling forward an archival log from a Linux client targeting a Windows server.

PSQL-6710

PDAC PvQuery returns a syntax error for a SELECT statement without a WHERE clause that retrieves a blob column.

PSQL-6732

“Communication Link Failure” returned by the ADO.NET provider when a SELECT parameter of type GUID is bound first to a value, and then to a NULL.

PSQL-6786

libpsqlmif.so is missing from the Android SDK.

PSQL-6802

An ADO.NET application inserting the first row in a table with BIGIDENTITY is getting the value 8589934592 instead of 1.

PSQL-6806

File opens can be slow in an environment with a large/remote active directory configuration.

PSQL-6824

Possible engine crash if specifying an empty string for a database name in front of the table name in a statement (i.e. SELECT * FROM “”.Person).

PSQL-6833

Possible status 43 returned from a DELETE statement containing a FULL OUTER JOIN.

PSQL-6861

Possible engine crash when executing a Stored Procedure containing a complex expression using local variables and the COALESCE() scalar function.

PSQL-6897

ADO.NET application executing a SELECT query with multiple ORDER BY columns that are BIGINT/UBIGINT may crash the engine.

PSQL-6898

Possible incorrect results from a SELECT query with a WHERE clause on a BIGIDENTITY column.

PSQL-6907

Possible incorrect results from an ADO.NET application executing a SELECT query with ORDER BY that includes a BIGIDENTITY column that is not the first listed.

PSQL-6909

Error “Data type in foreign key is invalid” returned when creating a foreign key on a BIGIDENTITY column.

PSQL-6984

Conversion error may be returned to a JDBC application using dynamic parameters for GUID and unsigned integer columns.

PSQL-7003

Export Schema fails to export very large view definitions.

PSQL-7004

Import Schema may fail to create a view that references other views.

PSQL-7033

Error “Unable to initialize DTI” may be returned to a 64-bit PDAC application.

PSQL-7047

Random status 3 could be returned to a multithreaded ADO.NET application.

PSQL-7078

Status 3014 returned when using an Ipv6 literal in a btrv: URI

PSQL-7079

Procedure or Function parameter should limit a varchar to 8000

PSQL-7107

MOD scalar function may return incorrect results with large values

PSQL-7132

Possible engine crash when BUTIL -PURGE on a file that is in the process of being closed

PSQL-7135

Client application crashes when calling an extended operation with a keybuffer allocated less than the key buffer length.

PSQL-7153

Possible engine crash when Selecting from multiple temp tables

PSQL-7159

Add PDAC support for RADStudio 10.3 Rio

PSQL-7195

Syntax error returned when using COUNT_BIG() in a subquery

PSQL-7204

“You are not authorized to perform this operation” returned when there is no valid license

PSQL-7208

‘Out of Range’ error returned when entering a negative value for a TINYINT with PCC add row.

PSQL-7210

Possible client application crash when a mix of components from v13 and v14 releases are found

PSQL-7224

Possible incorrect results with DATEDIFF/TIMESTAMPDIFF with Quarter or Week values

N/A

Added support for Windows Server 2019 and Windows 10 October 2018 Update

PSQL-5136

All remote communications may fail if the number of communication threads is set to a number larger than 256

PSQL-5507

PSQL Maintenance utility may report negative value for number of records

PSQL-5893

FILE.DDF and DBNAMES.CFG files can left open after multiple database access using PDAC with incorrect credentials

PSQL-5943

Adding or subtracting DATETIME/TIMESTAMP data may return incorrect fractional seconds

PSQL-5968

ALTER TABLE to add a column with a default value may not properly populate the new column in all cases

PSQL-5994

Create table after setting a default collating sequence can crash/close the engine on Linux

PSQL-6003

Converting integer value to Numeric or Decimal using TRY_CAST() may return “Error in row” or “Numeric value out of range”

PSQL-6009

PDAC can return status 35 if both local mapped Drive Letter and DDF location for the database on the server are the same

PSQL-6012

PCC may not return all results in Grid if the Select query includes subquery

PSQL-6024

After a cold reboot all PARC connections may not reopen

PSQL-6028

ALTER TABLE with PSQL_MOVE should not affect the data file when PSQL_PHYSICAL is not specified

PSQL-6030

ALTER TABLE to ADD a wide column with a DEFAULT may insert an incorrect default value

PSQL-6035

Engine can return status 103 when updating multiple non-nullable variable length columns in a single table

PSQL-6037

Collating a wide data type with “Upper.alt” should return “Invalid Collating Sequence”

PSQL-6082

INSERT with SELECT succeeds for a NOT NULL column with no DEFAULT defined when it should fail with “Column not nullable” error

PSQL-6091

Exporting Table schema is not including page compression attribute

PSQL-6131

INSERT with SELECT should fail with “Null not allowed” for a non-nullable column with no default value if the data selected is NULL

PSQL-6165

GetSchema() call may return negative ProviderDBTypes for Unicode data types NCHAR, NLONGVARCHAR and NVARCHAR

PSQL-6215

TRY_CONVERT function may return an error “statements in a UDF must have an argument”

PSQL-6218

Executing an update statement twice with dynamic parameters may return SQLBindParameter has not been called for parameter #4

PSQL-6222

Rebuild utility (rbldcli.exe) may crash rebuilding a remote file.

PSQL-6224

PCC importing data to a table with space(s) in name may fail with sql syntax error

PSQL-6227

ADO.NET 4.3 SDK install doesn't properly integrate with Visual Studio 2012 or 2013

     PSQL-6242

BCFG wait lock timeout range is incorrect

     PSQL-6245

The Pervasive Data Provider now supports .Net Core 2.0 and stores password information in encrypted form

PSQL-6247

PCC and Monitor utility may fail to load with the error “Premature end of file” due to a corrupt/missing configuration file

PSQL-6252

Delay in PCC when opening a large table

PSQL-6253

DSNADD may return “No driver found” when run on Raspbian Linux

PSQL-6262

Grant Execute on Stored Procedure may crash engine if the stored procedure name contains space(s) and is not in double quotes

PSQL-6282

Can’t “Select All” with a  right click to select all  the results from a PCC query

PSQL-6291

Casting a Float to a Timestamp may return an “incompatible data type” error

PSQL-6306

New PSQL install may write the number of I/O threads same as the number if cores on the system

PSQL-6307

SQL engine may crash when a scalar function is used on a longvarchar column

PSQL-6334

DDFBuilder may not save a table definition for a file with a “no-read-allowed” owner name

PSQL-6385

When running two Alter tables consecutively and if the first one fails the next Alter table may crash engine.

PSQL-6416

Delete statement may get Data Truncation error when using milliseconds value

PSQL-6467

Invalid Cast Exception may occur on executing a Stored Procedure if the SP contains GUID datatype

PSQL-6469

ADO.NET provider may return bracket for a "QuoteIdentifier"  call

 Tracking Number

Description

PSQL-5943

PSQL engine can now return  values in nanoseconds when TIMESTAMP values are added or subtracted

PSQL-5968

Alter table Add with Default String using Unicode driver can return incorrect  values

PSQL-5994

Create table after setting a default collating sequence can crash/close the engine on Linux

PSQL-6009

PDAC can return status 35 if both local mapped Drive Letter and DDF location for the database on the server are the same

PSQL-6012

PCC may not return all results in Grid if the Select query includes subquery

PSQL-6024

After a cold reboot all PARC connections may not reopen

PSQL-6028

ALTER TABLE with PSQL_MOVE should not affect the data file when PSQL_PHYSICAL is not specified

PSQL-6035

Engine can return status 103 when updating multiple non-nullable variable length columns in a single table

NA

PSQL V13.11 update 3  is tested with Windows 10 April 2018 Update

 Tracking Number

Description

PSQL-5035

Substring with out of range parameters may not return correct results

PSQL-5104

Updated the reporting engine so that it can no longer be accessed from a remote client due to licensing issues

PSQL-5392

Select from joined views with ambiguous column references should return an error

PSQL-5446

Insert into view with incorrect number of values should return an error

PSQL-5462

SELECT <table name>.*, C1 followed by an ORDER BY on C1 may not sort results correctly

PSQL-5469

Select with “like '%\%\%\%%” may not find values with three consecutive % characters

PSQL-5495

PCC exports data with embedded double quote characters (") incorrectly; they should be exported as ""

PSQL-5503

Errors returned from a Btrieve Extended Operation using the “LIKE” operator are not written to PVSW.LOG

PSQL-5520

SQL Query from a client using a static cursor may be slower than a forward-only cursor