PSQL muutokset versioittain
Uudet ominaisuudet
PSQL 13
PSQL 12
PSQL 11
Korjaukset
PSQL 13
Specific issues addressed in patch release (Build 13.31.015):
|
|
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. |
Previous issues addressed since release PSQL v13.30:
|
|
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 |
Specific issues addressed in patch release (Build 13.21.007):
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 |
Specific issues addressed in patch release (Build 13.11.014):
|
|
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 |
Previous issues addressed since release PSQL v13.10:
|
|
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 |
PSQL-5522 | SQL engine may not optimize on an available index for a restriction using IN |
PSQL-5538 | Table schema export is not including the ISR collation |
PSQL-5546 | A user without ALTER rights should not be allowed to rename objects in a secured database |
PSQL-5499 | The Kanji folder name in the PVSW.LOG on a Japanese OS is sometime not readable |
PSQL-5552 | Performance improvement for processing an IN subquery with mismatched datatypes |
PSQL-5598 | Visual Studio Integration service using the non-Unicode ODBC driver may return garbled database names |
PSQL-5625 | The command line phone authorization utility (clipaadm/w64clipaadm) may freeze on some Japanese machines |
PSQL-5629 | Query with three or more joined tables and a subquery may not be optimized when using a Forward Only cursor |
PSQL-5630 | Export Schema may return "No match available" when exporting a database that has COLLATE in a column name |
PSQL-5631 | ADO.NET provider may return "Input string was not in a correct format" when updating a DataGrid |
PSQL-5658 | SQLBindParameter error may occur when executing the same statement with different values in a python ODBC application |
PSQL-5678 | Calling a User Defined Function with a non-ASCII character in its name in a database with a non-default code page may return “Invalid user-defined or scalar function” |
PSQL-5689 | Possible SQL engine crash due to non-unique temp table names generated by the engine |
PSQL-5711 | Incorrect file name created when using non-ASCII characters in the name passed to the FileCreate method of the Btrieve 2 API via Python 3.x |
PSQL-5717 | GetCurrentDirectory using Btrieve 2 API via Python may return corrupted strings when the current directory contains non-ASCII characters |
PSQL-5718 | SQL Engine may crash on a query with the same column repeated >250 times in the ORDER BY |
PSQL-5730 | Possible engine crash when one connection handle tries to drop a table that is in use, and another connection tries to fetch data from the table. |
PSQL-5747 | PARC and Wire Encryption (Always) enabled may affect ODBC performance |
PSQL-5763 | “Unknown provider error” when inserting/deleting data through MS Linked Server 2016 and later |
PSQL-5777 | Engine may hang using Backup Agent to backup files which are under defragmentation |
PSQL-5778 | Select query with segmented index with a varchar column with more than 255 bytes may return incorrect data |
PSQL-5804 | PSQL Engine may crash if the temporary index created for an ORDER BY/GROUP BY/DISTINCT/etc. is more than 250 bytes and the query uses Static/Dynamic cursor |
PSQL-5811 | Improved Cache Engine Performance on first read |
PSQL-5844 | CREATE/DROP/ALTER table with IN DICTIONARY may update existing PK/FK relationships incorrectly |
PSQL-5856 | Incorrect client version format in a JDBC connection string may crash the engine |
PSQL-5880 | Complex query with a view using several outer joins may crash the engine |
PSQL-5882 | Added PDAC support for RAD Studio V10.2(Tokyo) |
Specific issues addressed in patch release (Build 13.01.010):
PSQL-4300 | PCC is not closing the JDBC sessions associated with its main screen correctly |
PSQL-4628 | With Forward only cursor SQLExecute may not double the number of rows with an “INSERT INTO tbl SELECT * FROM tbl” statement |
PSQL-4720 | PSQL System SP psp_columns call returns “not nullable” for legacy tables |
PSQL-4747 | Psql Odbc Unicode driver may return only first Japanese character of the error message |
PSQL-4859 | Engine may Incorrectly spawn extent file though limit Segment Size setting is disabled |
PSQL-5002 | ORDER BY with COLLATE on SELECT statement may return incorrect results first time run |
PSQL-5060 | High connection load may buildup handles for login credentials can result in memory leaks |
PSQL-5098 | Manual authorization may return Status 7113 for a valid Workgroup deployment |
PSQL-5168 | select @@spid may return the same id number on a second connection on Linux |
PSQL-5191 | BUTIL syntax output is missing a <cr><lf> at the end of the BUTIL -ROLLFWD line |
PSQL-5262 | Partial Index attribute is not properly displayed in PCC for multi-segment partial indexes |
PSQL-5263 | ][SQL Engine][Data Record Manager] (11390) error may be returned when using Dynamic cursor with "SELECT TOP/LIMIT" |
PSQL-5269 | Incorrectly defined PSQL system tables may crash PSQL engine in some cases |
PSQL-5279 | TCP is now the only supported communication protocol |
PSQL-5308 | Engine may not return all the records when a string constant part of a segmented key is longer than the field length |
PSQL-5333 | “Error in Expression” should be returned in queries that have non-uniquely identified columns |
PSQL-5347 | Large query with CASE and many "OR" may hang the engine |
PSQL-5387 | Trigger may not work if the database path format in the connection string doesn't match with dictionary path |
PSQL-5392 | Corrected to return error on merge-able views without uniquely identified columns |
PSQL-5407 | A Btrieve file may divide at 4GB if the engine is running under an account that does not have sufficient rights to query the hard drive configuration |
PSQL-5447 | “Duplicate column found in insert list.” was not being returned in some cases |
PSQL-5462 | Results may be sorted incorrectly when ORDER BY includes an aliased column listed after table.* in the select list |
PSQL-5495 | PCC Export data should export embedded double quotes in strings with two double quotes |
PSQL-5522 | SQL engine may not optimize on an available index for a restriction using IN |
PSQL-5546 | ALTER RENAME can allow objects to be renamed in a secure db by a user without Alter rights |
Previous issues addressed since release PSQL v13.00
|
|
PSQL-3992 | Export Table Schema in PCC fails to export default if it is a single space |
PSQL-4633 | Possible hang in the SQL Manager when many connect requests come in from different clients at the same time |
PSQL-4808 | Bulk insert via ODBC with multiple dynamic parameters set to be null may cause the engine to crash |
PSQL-4832 | Incorrect results returned using multiple restrictions on an indexed date column with different operators, such as = and BETWEEN |
PSQL-4856 | 64-bit SQL engine may crash with very large query involving 2000+ conditions in the WHERE clause |
PSQL-4864 | IN subquery on columns with different data types (such as VARCHAR and INTEGER) may never return |
PSQL-4969 | Incorrect number of rows may be returned when non-leading index segment is defined as CHAR when ansi_padding is off |
PSQL-4981 | "SELECT * FROM X$User" is slow to return when USER.DDF is missing |
PSQL-5006 | Abnormally ending a SQL connection on a Linux server may cause other connections to crash |
PSQL-5033 | Complex query generating multiple temp tables with nested table subqueries returning a LONGVARCHAR column using a forward-only cursor may crash the SQL engine |
PSQL-5060 | Excess handles allocated and not released due to legacy delay in communication components. |
PSQL-5078 | SQLColumns may return multiple instances of columns in some cases with very large databases |
PSQL-5101 | PCC should prompt to restart engine when changing the “Use Cache Engine” setting |
PSQL-5148 | Query with CASE in the outer SELECT list and the SELECT list of a table subquery may crash the SQL engine |
PSQL-5154 | BDU may return "DataLoader | 22: The data buffer parameter is too short" when the data file has many keys. |
PSQL-5163 | Status 84 may be returned after issuing a SELECT FOR UPDATE query that has an empty result set |
PSQL-5164 | Updated Setup<product_type>_<platform>.exe launchers address an error 1723 during install |
PSQL-5171 | Buffer overflow not detected on direct communication to port 1583/3351 |
PSQL-5185 | Corrupt file causes a divide by zero crash in the MKDE |
PSQL-5190 | Old PSQL Logo displayed in PCC Preferences |
PSQL-5193 | Actian PSQL Perfmon counters are not properly registered after upgrade install |
PSQL-5194 | PSQL install/patch on Windows 10 with limited resources uses 100% CPU and does not terminate properly |
PSQL-5208 | Complex query with CASE and table subqueries with joins may return a Syntax Error |
PSQL-5217 | BDU is not properly handling empty strings and null entries from import file |
PSQL-5247 | Status 5 returned when creating a table in a database where X$Field already has an ID=65535 |
PSQL-5248 | Add support for PARTIAL index in Schema Export/Import |
PSQL 12
Specific issues addressed in patch release (Build 12.11.033):
|
|
PSQL-6251 | SQL/JDBC connections sometimes take several minutes to connect to the engine. |
PSQL-6291 | Casting a Float to a Timestamp may return an “incompatible data type” error. |
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-6385 | When running two Alter tables consecutively and if the first one fails the next Alter table may crash engine. |
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-6416 | Delete statement may get Data Truncation error when using milliseconds value. |
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-6492 | Queries with LIKE run much slower in a non-English code page 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-6615 | Possible incorrect results with NULLIF() scalar function when used with a wide data type. |
PSQL-6627 | Possible incorrect results from a SELECT statement with a subquery combined with other optimizable restrictions. |
PSQL-6648 | Change SQL engine to use an internal lead-byte check instead of the MS function. |
PSQL-6710 | Syntax error returned to PDAC for a SELECT on a table with a variable length column when the SELECT has double quotes around the table name and does not have a WHERE clause. |
Previous issues addressed since release PSQL v12.10
|
|
PSQL-2367 | Applying updates on PSQL v12.10 is not updating the registry to 12.11.xxx |
PSQL-2585 | Trace requester treating 0x09 character as printable causing output to be skewed |
PSQL-3628 | Patching adds duplicate –data & -configuration lines to Builder.ini and PCC.ini |
PSQL-3737 | Possible performance hit in an environment with a large number of open & close requests on files undergoing heavy I/O. |
PSQL-3853 | Enhanced ADO.NET’s performance when using dynamic parameters which required Unicode character conversion |
PSQL-3858 | Syntax Error returned on nested table subqueries |
PSQL-3865 | Uninstall hangs if PSQL services are set to manual and stopped before uninstalling |
PSQL-3867 | SRDE allows multiple users into the database when setting security on database |
PSQL-3872 | PCC About menu on Linux displays the components version instead of the install version |
PSQL-3896 | SRDE may crash when using dynamic parameter for TIMESTAMP column in IN clause |
PSQL-3897 | SQL engine may crash when executing a query on joined tables with a non-correlated subquery on one of the same tables |
PSQL-3899 | Status 19 returned when updating multiple files with different file version in a transaction |
PSQL-3921 | Memory leak in PvTable.SetRange |
PSQL-3926 | Upgrade to v12 SP1 from v11 Client 64 on WGE32 may corrupt machine.config for ADO.NET |
PSQL-3927 | “Error in Expression” is returned if first parameter of the REPLACE() scalar is dynamic |
PSQL-3956 | Query with IN clause on a subquery using TOP returns incorrect results |
PSQL-3992 | Export Table Schema in PCC fails to export default if it is a single space |
PSQL-3993 | Status 148 being returned from defragmenter |
PSQL-4012 | Identical SELECT query returns different results when run again |
PSQL-4065 | SQL Engine may crash when dropping a database while logged into a different database. |
PSQL-4069 | SELECT TOP with scrollable cursor returns incorrect rows |
PSQL-4075 | Engine stops responding when processing Stored Procedure with columns using Unicode names |
PSQL-4081 | Cannot create Stored Procedure if there is a SQL reserved words in the PRINT statement |
PSQL-4084 | Engine returns error -5099 when executing stored procedures that mix UTF-8 and DBEnc formats "Unable to open table" |
PSQL-4090 | Correlated query using EXISTS or IN or ANY/ALL may return incorrect results |
PSQL-4095 | Misconfigured Windows user may cause Engine crash when connecting via DTI/DTO |
PSQL-4099 | Non-segmented file with final size > 4GB becomes corrupted after defragmenting |
PSQL-4104 | Multiple issues with SELECT TOP were addressed |
PSQL-4120 | Top n returns incorrect results with scrollable cursor with SQL_FETCH_ABSOLUTE |
PSQL-4181 | Maintenance Utility error message is truncated |
PSQL-4187 | ODBC sessions disconnect after 7 hours if Pervasive Auto Reconnect is on |
PSQL-4284 | Possible status 3116 returned from Client Cache Engine under load |
PSQL-4291 | MKDE hangs instead of returning status 2 when accessing a corrupted file |
PSQL-4293 | Can now use NULL in selection list of an IF clause |
PSQL-4296 | OLE-DB Provider returns invalid column definition when using MS Linked Server |
PSQL-4301 | PCC database properties displays relational constraints incorrectly |
PSQL-4302 | “Error in Predicate" returned for SELECT … WHERE <constant> IN subquery |
PSQL-4304 | Resizing GUI Defragmenter window returns "index out of range" error |
PSQL-4307 | DDFBuilder returns Eclipse error when opening a table |
PSQL-4309 | Table subquery with UNION and ORDER BY DESC may return incorrect results |
PSQL-4329 | Disable "Page server invalidation list is full" message |
PSQL-4331 | Defragmenter stuck in Commit Pending due to VSS |
PSQL-4336 | Correlated subquery with UNION returns “General Error” |
PSQL-4382 | Linux Server crash processing inserts from UTF-8 encoded CSV file |
PSQL-4384 | Cache engine can skip periodic page-invalidation requests |
PSQL-4386 | Using Cache Engine may return 3116 errors |
PSQL- 4392 | DDFBuilder sometimes does not display key segments properly |
PSQL-4393 | PSQL v12 cannot handle multibyte string path with in 255 bytes as ShiftJIS |
PSQL-4410 | Subquery using UNION returns unknown prefix ‘View4Tab1’ error |
PSQL-4411 | SELECT with WHERE clause on non-indexed string field returns empty grid in PCC |
PSQL-4418 | Query with ANSI-PADDING off requiring temp file returns different results on second execution |
PSQL-4429 | Inconsistent results using ANY (subquery) with VARCHAR versus LONGVARCHAR field |
PSQL- 4433 | For the PSQL Client on a 32-bit Windows OS, the version is not properly updated after patching |
PSQL- 4434 | Patching the PSQL 12 Workgroup Engine on a 32-bit OS produces an unnecessary “InstallDir64” registry entry |
PSQL-4438 | Possible incorrect results using extended operations when CACHE Engine is enabled |
PSQL-4446 | Security on metadata v2 database should not add ALL rights to PUBLIC on existing SP/UDF/Views |
PSQL-4473 | PDAC is updated to support Delphi 10.1(Berlin) |
PSQL-4479 | Collating sequence name not showing up in column properties of table in metadata v2 database |
PSQL- 4484 | ADO.NET 4.2 updated to support Entity Framework 6 |
PSQL-4511 | Cache engine may hang under heavy load with multiple cache engines accessing shared files. |
PSQL-4518 | Nested subqueries within a table subquery may return “Error in expression” |
PSQL-4520 | Subquery table with TOP expression and alias COM2 returns "Invalid view or table name” |
PSQL-4524 | SELECT query with IF expressions returns incorrect results with ANSI_PADDING set to OFF |
PSQL-4534 | SELECT INTO with an expression subquery can fail with the error "Table or view already exists." |
PSQL-4566 | DROP PROCEDURE with more than one space at the end returns a syntax error |
PSQL-4578 | Possible crash with four or more SELECT queries using a LIKE operator combined with UNION |
PSQL-4579 | Running the same parameterized query many times in a loop may fail with a SQLBindParameter error |
PSQL-4581 | ADO.NET Provider returns incorrect results for query with more than two statements combined with 'union all' |
PSQL-4617 | Possible incorrect values used when executing multiple SQL statements from the same statement handle, and changing parameters for each statement. |
PSQL-4619 | Data truncated when fetching multiple rows with longvarchar/longvarbinary data |
PSQL-4627 | ADO.NET provider generates PsqlException on datatable fill method on Select with IFNULL function |
PSQL-4628 | With Forward only cursor SQLExecute may not double the number of rows with an “INSERT INTO tbl SELECT * FROM tbl” statement |
PSQL-4633 | Possible hang in the SQL Manager when many connect requests come in from different clients at the same time |
PSQL-4669 | Length & RTRIM scalar functions return incorrect results when ANSI_PADDING=OFF |
PSQL-4675 | Linux Monitor may show IP and hostname as "0.0.0.0" / "Unknown user" for application running locally |
PSQL-4681 | Engine should check for multiple consecutive key segments in TEMP tables for optimization |
PSQL-4684 | Cache engine may hang under load |
PSQL-4707 | Updated Ado.net sdk sample project "Escapes" to fix compiling error |
PSQL-4708 | Revoking individual rights after granting all rights on a table to a particular user can deny all rights to that users |
PSQL-4720 | System SP call psp_columns can return columns as “not nullable” on legacy tables |
PSQL-4739 | ADO.NET provider may return intermittent errors such as System.FormatException or System.Data.ConstraintException in a high volume multi-threaded environment |
PSQL-4747 | Psql Odbc Unicode driver may return only first Japanese character of the error message |
PSQL-4778 | Cache engine crash due to a memory overwrite of an incorrect keybuffer |
PSQL-4779 | AnsiPadding setting is causing incorrectly padded strings to be returned |
PSQL-4782 | Accessing a corrupt file may crash engine due to specific key page corruption |
PSQL-4796 | Specifying a COLLATE attribute on a non-string column in a CREATE/ALTER table could produce status 49: "Key Type is invalid" when creating an index on the column |
PSQL-4808 | Bulk insert via ODBC with multiple dynamic parameters set to be null may cause the engine to crash |
PSQL-4832 | Incorrect results returned using multiple restrictions on an indexed date column with different operators, such as = and BETWEEN |
PSQL-4839 | SQL engine may hang or crash when reading a view definition that is an exact multiple of 1996 bytes |
PSQL-4844 | Creating a legacy table with a LOGICAL column that has a DEFAULT can return Unknown Error: -19 |
PSQL-4853 | Linux PCC monitor for MicroKernel Sessions displays "Remote" for "Local" applications |
PSQL-4856 | 64-bit SQL engine may crash with very large query involving 2000+ conditions in the WHERE clause |
PSQL-4859 | When file gets to the maximum possible size, the engine may incorrectly spawn a new extension file |
PSQL-4864 | IN subquery on columns with different data types (such as VARCHAR and INTEGER) may never return |
N/A | Added support for Windows 10 Creators |
PSQL-4930 | Incorrect number of records displayed in PCC grid when a query has an embedded comment including “WHERE” |
PSQL-4969 | Incorrect number of rows may be returned when non-leading index segment is defined as CHAR when ansi_padding is off |
PSQL-4981 | "SELECT * FROM X$User" is slow to return when USER.DDF is missing |
PSQL-5002 | ORDER BY with COLLATE on SELECT statement can return incorrect results |
PSQL-5006 | Abnormally ending a SQL connection on a Linux server may cause other connections to crash |
PSQL-5029 | Possible engine crash due to memory corruption caused by many nested data type conversions |
PSQL-5033 | Complex query generating multiple temp tables with nested table subqueries returning a LONGVARCHAR column using a forward-only cursor may crash the SQL engine |
PSQL-5034 | A select with a UNION and a User Defined Function in an Order By may crash the engine |
PSQL-5035 | Substring with out of range parameters may not return correct results |
PSQL-5060 | Excess handles allocated and not released due to legacy delay in communication components. |
PSQL-5078 | SQLColumns may return multiple instances of columns in some cases with very large databases |
PSQL-5098 | Update to GUI phone authorization utility for status 7113/7215 issue |
PSQL-5101 | PCC should prompt to restart engine when changing the “Use Cache Engine” setting |
PSQL-5148 | Query with CASE in the outer SELECT list and the SELECT list of a table subquery may crash the SQL engine |
PSQL-5154 | Status 22 returned by BDU when loading data into table with many indexes, even though data is loaded correctly. |
PSQL-5163 | Status 84 may be returned after issuing a SELECT FOR UPDATE query that has an empty result set |
PSQL-5168 | select @@spid may return the same id number on a second connection on Linux |
PSQL-5171 | Buffer overflow not detected on direct communication to port 1583/3351 |
PSQL-5185 | Corrupt file causes a divide by zero crash in the MKDE |
PSQL-5208 | Complex query with CASE and table subqueries with joins may return a Syntax Error |
PSQL-5217 | BDU is not properly handling empty strings and null entries from import file |
PSQL-5247 | Status 5 returned when creating a table in a database where X$Field already has an ID=65535 |
PSQL-5263 | ADODB application with SELECT TOP/LIMIT using ODBC can return [ SQL Engine][Data Record Manager] (11390) error |
PSQL-5269 | Incorrectly created DDFs using third party tools can result in engine crash |
PSQL-5308 | Possible incorrect results from query comparing an indexed string constant that is longer than the column length |
PSQL-5333 | “Error in Expression” should be returned in queries that have non-uniquely identified columns |
PSQL-5347 | Poor performance of query with a CASE statement that includes many OR predicates |
PSQL-5387 | Trigger may not work if the database path format in the connection string doesn't match with dictionary path |
PSQL-5439 | Function Executor can now show the correct file size over 2GB on the statistics window |
PSQL-5446 | Insert into view with incorrect number of values should return an error |
PSQL-5447 | “Duplicate column found in insert list.” was not being returned in some cases |
PSQL-5462 | Results may be sorted incorrectly when ORDER BY includes an aliased column listed after table.* in the select list |
PSQL-5469 | Select with “like '%\%\%\%%” may not find values with three consecutive % characters |
PSQL-5495 | PCC Export data should export embedded double quotes in strings with two double quotes |
PSQL-5499 | The Kanji folder name in the PVSW.LOG on a Japanese OS is sometime not readable |
PSQL-5520 | SQL Query from a client using a static cursor may be slower than a forward-only cursor |
PSQL-5522 | SQL engine may not optimize on an available index for a restriction using IN |
PSQL-5538 | Table schema export is not including the ISR collation |
PSQL-5546 | ALTER RENAME can allow objects to be renamed in a secure db by a user without Alter rights |
PSQL-5598 | Visual Studio Integration service using the non-Unicode ODBC driver may return garbled database names |
PSQL-5629 | Query with three or more joined tables and a subquery may not be optimized when using a Forward Only cursor |
PSQL-5631 | ADO.NET provider may return "Input string was not in a correct format" when updating a DataGrid |
PSQL-5658 | SQLBindParameter error may occur when executing the same statement with different values in a python ODBC application |
PSQL-5678 | Calling a User Defined Function with a non-ASCII character in its name in a database with a non-default code page may return “Invalid user-defined or scalar function” |
PSQL-5689 | Possible SQL engine crash due to non-unique temp table names generated by the engine |
PSQL-5718 | SQL Engine may crash on a query with the same column repeated >250 times in the ORDER BY |
PSQL-5747 | PARC and Wire Encryption (Always) enabled may affect ODBC performance |
PSQL-5763 | Unknown provider error” when inserting/deleting data through MS Linked Server 2016 and later |
PSQL-5777 | Running PSQL Defrag and backup simultaneously on the same file(s) may hang the engine |
PSQL-5778 | Incorrect results from a query with multiple restrictions matching an index, plus an extra restriction on a varchar(255) column |
PSQL-5811 | Improved Cache Engine Performance on first and repeated reads |
PSQL-5844 | CREATE/DROP/ALTER table with IN DICTIONARY may update existing PK/FK relationships incorrectly |
PSQL-5856 | Incorrect client version format in a JDBC connection string may crash the engine |
PSQL-5880 | Possible SQL engine crash from complex multi-join query with an invalid view column |
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-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 |
PSQL-6082 | INSERT with SELECT succeeds for a NOT NULL column with no DEFAULT defined when it should fail with “Column not nullable” error |
N/A | PSQL V12.11 update 12 is tested with Windows 10 April 2018 Update |
PSQL-6131 | Insert with Select doesn’t work for a non nullable column with no default value |
PSQL-6201 | BDU importing data with “comas” in a field may fail |
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-6252 | PCC may Table Scans all records of a table when opened |
PSQL-6262 | Grant Execute on Stored Procedure may crash engine if the stored procedure name contain space(s) |
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-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 |
Specific issues addressed in patch release (Build 12.01.071):
|
|
PSQL-2585 | Trace requester treating 0x09 character as printable causing output to be skewed |
PSQL-3628 | Patching adds duplicate –data & -configuration lines to Builder.ini and PCC.ini |
PSQL-3905 | DDFBuilder edit table sql view repeats last 2 unicode characters |
PSQL-4012 | Incorrect results from SELECT with table subquery and mixed AND & OR predicates |
PSQL-4065 | SQL Engine may crash when dropping a database while logged into a different database. |
PSQL-4069 | SELECT TOP with scrollable cursor returns incorrect rows |
PSQL-4075 | Engine stops responding when processing Stored Procedure with columns using Unicode names |
PSQL-4081 | Cannot create Stored Procedure if there is a SQL reserved words in the PRINT statement |
PSQL-4084 | Engine returns error -5099 when executing stored procedures that mix UTF-8 and DBEnc formats "Unable to open table" |
PSQL-4090 | Correlated query using EXISTS or IN or ANY/ALL may return incorrect results |
PSQL-4095 | Misconfigured Windows user may cause Engine crash when connecting via DTI/DTO |
PSQL-4104 | Multiple issues with SELECT TOP were addressed |
PSQL-4120 | Top n returns incorrect results with scrollable cursor with SQL_FETCH_ABSOLUTE |
PSQL-4181 | Maintenance Utility error message is truncated |
PSQL-4187 | ODBC sessions disconnect after 7 hours if Pervasive Auto Reconnect is on |
PSQL-4291 | MKDE hangs instead of returning status 2 when accessing a corrupted file |
PSQL-4293 | Can now use NULL in selection list of an IF clause |
PSQL-4296 | OLE-DB Provider returns invalid column definition when using MS Linked Server |
PSQL-4301 | PCC database properties displays relational constraints incorrectly |
PSQL-4302 | “Error in Predicate" returned for SELECT … WHERE <constant> IN subquery |
PSQL-4307 | DDFBuilder returns Eclipse error when opening a table |
PSQL-4309 | Table subquery with UNION and ORDER BY DESC may return incorrect results |
PSQL-4336 | Correlated subquery with UNION returns “General Error” |
PSQL-4382 | Linux Server crash processing inserts from UTF-8 encoded CSV file |
PSQL-4393 | PSQL v12 cannot handle multibyte string path with in 255 bytes as ShiftJIS |
PSQL-4410 | Subquery using UNION returns unknown prefix 'View4Tab1' error |
PSQL-4418 | Query with ANSI-PADDING off returns different results on second execution. |
PSQL-4429 | Inconsistent results using ANY (subquery) with VARCHAR versus LONGVARCHAR field |
Previous issues addressed since release PSQL v12.00
|
|
PSQL-1313 | Btrieve file version incorrect in Linux PCC |
PSQL-1998 | Possible status 3 during defragment validation process |
PSQL-2121 | Data truncation not reported for Unicode default values |
PSQL-2138 | Error messages from SRDE are in English and not Japanese for PSQL-J |
PSQL-2159 | On a Japanese OS the ADO.NET sample program LongDataTypes does not work |
PSQL-2160 | ADO.NET Data Provider's DataReader cannot read NLONGVARCHAR string data over 4K bytes in length |
PSQL-2222 | Defragmenter Error 125 on segmented file |
PSQL-2247 | Application crashes when trying to open Btrieve file on non-existent drive mapping |
PSQL-2275 | Fujitsu Cobol ODBC sample is not working correctly with Psql ODBC |
PSQL-2280 | Periodic error message ‘Animation Start’ in Pervasive Control Message |
PSQL-2285 | PVSW.Log has excessive messages, “the system cache will be used for file” |
PSQL-2287 | Data truncation error on Select statement with GROUP BY on LONGVARCHAR column |
PSQL-2297 | Constraint in Create statement does not create index |
PSQL-2298 | Cross Join query with table subquery may crash database engine |
PSQL-2327 | Memory leak in PDAC TPVQuery on table with LONGVARCHAR or NOTE field. |
PSQL-2330 | Table column and procedure column defaults not always working correctly |
PSQL-2331 | Unicode ODBC driver's SQLGetInfo call for SQL_DBMS_NAME returns garbage |
PSQL-2337 | Add Wire Encryption for PCC JDBC Connections |
PSQL-2338 | ISQL on linux doesn't display all characters when talking to windows server |
PSQL-2344 | Incorrect results on nchar without length |
PSQL-2345 | IIS application crashes with heap corruption on W3ODBCCI.DLL |
PSQL-2348 | Constraint in Create statement does not create index |
PSQL-2362 | Updates don't work on the 12.00.163 Japanese release |
PSQL-2377 | Updated PSQL ADO.NET 4.0 provider: - PsqlDataAdapter does not work with Japanese named tables - Stored Procedure returns ‘invalid cast’ error |
PSQL-2397 | Deleting database name on bound database was deleting the ddfs |
PSQL-2398 | 'Fragmented', 'Unused', and 'Not in order' percentages are all zero for file even after much use in defragmenter |
PSQL-2399 | PSQL Services have trouble starting with Anti-Virus product Installed |
PSQL-2414 | SQL Engine crash with query including a User Defined Function that returned many rows |
PSQL-2427 | PSQL Engine crashes when ordered by is used in a select statement containing a very large NLONGVARCHAR |
PSQL-2431 | Creating Table with ACS Causes DDF Builder to fail |
PSQL-2432 | Deleting Table with ACS Causes DDF Builder to fail |
PSQL-2433 | PCC Grid's Status Bar does not update correctly |
PSQL-2449 | Problem using ODBC translation dll under Psql v12 |
PSQL-2451 | Get Direct/Chunk with 'next in blob' may fail with error 106 after rebuild on 32 bit Window engines |
PSQL-2467 | Updated the postinstall.sh file in Linux |
PSQL-2473 | Bind/unbind v2 metadata returns "General_Error" |
PSQL-2475 | ADO.NET install on Japanese operating system does not properly update .Net Framework machine.config file |
PSQL-2479 | Before Defrag stats truncated in the GUI summary panel |
PSQL-2530 | Unicode driver issue with CURRENCY fields with value < 1 |
PSQL-2548 | JCL error 3103 when URI contains Domain\\username |
PSQL-2557 | JCL Connection using domain name is returning status 3103 |
PSQL-2569 | Post defrag handling of extended inserts may not be handled correctly |
PSQL-2570 | Decimal precision not handled properly in some cases |
PSQL-2571 | CAST decimal value as CHAR should maintain 0 place holders |
PSQL-2574 | Engine may crash when defragging file with fixed record size > 31k |
PSQL-2589 | Export table schema fails to include CR on each line of output file |
PSQL-2599 | Problem opening Btrieve file when working directory cannot be changed. |
PSQL-2629 | Possible crash when fetching with one handle and executing a drop table from another handle using the same sql connection |
PSQL-2632 | Possible crash rebuilding large segmented file into single segment file using file maintenance |
PSQL-2635 | Incompatible types in expression error after creating an index on one of the columns in the query.in ODBC application |
PSQL-2638 | Repair Bound database is not padding the Database Name with spaces |
PSQL-2642 | A Rebuild Analyze during a Rebuild improperly clears the "Under Rebuild" flag |
PSQL-2643 | IFNULL/ISNULL() in other scalar functions causes "Expression evaluation error" |
PSQL-2650 | Defrag may handle file segmentation incorrectly during defragmentation. |
PSQL-2654 | Analyzing a file during defragmentation may cause it to fail with error 125 |
PSQL-2658 | "Out of Memory" error may occur using distinct and concat on nlongvarchar columns |
PSQL-2665 | PCC Displays Incorrect Version Number |
PSQL-2677 | Multiple triggers on same table are not respecting execution ORDER specified |
PSQL-2679 | The ADO.NET 4.2 Provider sample project LongDataTypes displays error "Unable to read beyond the end of the stream." when the Stream Object button is clicked. |
PSQL-2725 | ADO.Net returns “incompatible types in expression” after creating an index on one of the columns in the query |
PSQL-2774 | SQL statement is not returning the right results with ANSI_PADDING=off with temp table |
PSQL-2779 | SQL statement not executed in PCC on Japanese OS because of unpaired single quotes in a comment |
PSQL-2794 | Character conversion on Japanese OS is slower for 32-bit ODBC |
PSQL-2789 | ADO.NET fails with random error if there are nested datareaders |
PSQL-2838 | Monitor and Defrag utility may not come up on boxes with 32 or more processors |
PSQL-2960 | IndexoutOfRange exception may be returned by PSQL ADO.NET 4.0 and 4.1 providers when executing a stored procedure with a RETURNS clause |
PSQL-3010 | ADO.NET connections fail with Japanese named databases when using ADO.NET 4.2 Provider |
PSQL-3018 | Currency Not On Record error returned with Case expression in WHERE clause |
PSQL-3020 | Currency Not on Record error with ORDER BY on temp table with Case Expression |
PSQL-3036 | File with 1K page size and page compression may become corrupt during rebuild |
PSQL-3042 | Underscore (_) in table name may cause other table’s columns to show in table properties |
PSQL-3043 | A table with only one column of less than 4 characters displays incorrectly in DDFBuilder |
PSQL-3045 | CREATE DATABASE statement with blanks in the DDF or Data path may cause status 11 or 35 |
PSQL-3046 | SRDE should create paths that do not exist when specified in CREATE DATABASE |
PSQL-3052 | Select from view with UNION and an invalid ORDER BY may crash the engine |
PSQL-3068 | PCC’s Monitor, Microkernel Communications Statistic Engine’s Uptime truncated at end of Japanese MAC |
PSQL-3073 | ADO.NET4.2 returns error when inserting double byte character into longvarchar data type |
PSQL-3110 | ADO.NET 4.1 provider: Stored Procedure INOUT parameter is not working with Command.Text |
PSQL-3177 | CREATE TABLE with USING clause specifying a path that does not exist should create the necessary folders and the file |
PSQL-3178 | CREATE…IN DICTIONARY…USING should succeed even if the specified file cannot be opened |
PSQL-3222 | Adding an owner name with encryption produced many extended files |
PSQL-3249 | Add support for the LINQ take() & skip() functions, and parameterized TOP queries for use in ODATA applications |
PSQL-3258 | PCC is repeating index columns when viewing indexes in the index view |
PSQL-3276 | OLEDB application may crash when inserting SQL_BINARY data into a NOTE column |
PSQL-3289 | UNION ALL query returns more records than expected when index used for IN list restriction |
PSQL-3310 | Incorrect results re-executing query with mixed UNION/UNION ALL and TOP clause |
PSQL-3337 | Continous Ops is logging messages for every file in pvsw.log |
PSQL-3340 | Re-executing batch sql statements with dynamic parameters may return SQLBindParameter errors |
PSQL-3353 | CREATE TABLE statement via SQLPrepare followed by SQLExecDirect may crash when using the Unicode ODBC driver |
PSQL-3379 | Defragmentation returned status 124 |
PSQL-3440 | Add support for PDAC XE8 and XE10 |
PSQL-3443 | Last character missing from longvarchar or nlongvarchar field on a SELECT INTO call |
PSQL-3452 | Make monitor max worker threads unlimited instead of displaying a value which exceeded 256 |
PSQL-3474 | Incorrect results with ANY/ALL with TOP query using dynamic parameters |
PSQL-3481 | Exception with message “Object reference not set to an instance of an object” from stored procedure execution in Entity Framework application. |
PSQL-3497 | Possible engine crash when dynamic parameter fails to indicate a large chunk of data as LONGVARCHAR |
PSQL-3531 | Substring did not handle arguments that referenced positions beyond the end of the string. |
PSQL-3549 | AM hook module crashes when opening file whose path is greater than 256 characters. |
PSQL-3557 | Incorrect results from using ACOS() scalar function when column is indexed |
PSQL-3575 | PCC displays message when it has run out heap memory loading a very large sql document |
PSQL-3576 | SQLProcedureColumns do return default value for UDF functions |
PSQL-3590 | Engine crashes when dropping a database if another database exists that points to the same location |
PSQL-3594 | Incorrect results when using SELECT DISTINCT on Unicode data type |
PSQL-3605 | Incorrect results from ADO.NET when executing stored procedure with select procedure into a temporary table followed by a select query. |
PSQL-3622 | Query Plan Viewer chops strings inside filter windows |
PSQL-3633 | Create Database SQL command creates unneeded Windows Folder in Japanese PSQL version |
PSQL-3658 | Access violations in PDAC when using CURRENCY and LONGVARBINARY datatypes |
PSQL-3659 | PSQL Engine stops responding on SQL query with excessive predicates |
PSQL-3665 | Maximum number of sort columns exceeded error return from forward only cursor |
PSQL-3666 | IP address shown in AMViewer from remote clients is not correct |
PSQL-3671 | Query with static/dynamic cursor returns different results |
PSQL-3702 | SQL Engine returns Memory Allocation Error while running query |
PSQL-3719 | Message to close Notification Viewer is confusing in cluster environment |
PSQL-3723 | Possible crash in w3odbci.dd when PARC is enabled |
PSQL-3765 | Invalid cursor state returned by execute (‘create view v1 (vc1) as select 1’) |
PSQL-3784 | ADO.NET 4.2 provider sending incorrect parameter set to server when query has multiple statements with parameters passed in ANSI mode |
PSQL-3796 | Locate function in Stored Procedure does not work as expected |
PSQL-3814 | PCC’s text window was not scrolling properly to display results from DDL statements |
PSQL-3853 | Enhanced ADO.NET’s performance when using dynamic parameters which required Unicode character conversion |
PSQL-3858 | Syntax Error returned on nested table subqueries |
PSQL-3865 | Uninstall hangs if PSQL services are set to manual and stopped before uninstalling |
PSQL-3867 | SRDE allows multiple users into the database when setting security on database |
PSQL-3881 | Removed PSA’s dependency on keyhelp.ocx |
PSQL-3896 | SRDE may crash when using dynamic parameter for TIMESTAMP column in IN clause |
PSQL-3897 | SQL engine may crash when executing a query on joined tables with a non-correlated subquery on one of the same tables |
PSQL-3899 | Status 19 returned when updating multiple files with different file version in a transaction |
PSQL-3921 | Memory leak in PvTable.SetRange |
PSQL-3925 | Client64 installed on WGE environment corrupts ADO.NET machine.config when updates are applied to it |
PSQL-3927 | “Error in Expression” is returned if first parameter of the REPLACE() scalar is dynamic |
PSQL-3956 | Query with IN clause on a subquery using TOP returns incorrect results after update 7 was applied |
62463 | Engine may crash creating index on large file because of a problem related to page compression |
62469 | Incorrect first row may be returned from Stored Procedure calling SELECT with GROUP BY |
62471 | IFNULL returns Expression Evaluation Error |
62473 | Random PDAC access violation errors using TPVQuery to retrieve data |
62474 | Possible crash on query containing parameterized value if incorrectly resolved. |
62475 | System.Access.ViolationException seen on ADODB.RecordSetClass.Move with dynamic cursor |
62480 | “Null not Valid” returned from view which has an UDF. |
PSQL 11
Specific issues addressed in Patch release (Build 11.31.101):
Tracking Number | Description |
PSQL-3222 | Adding an owner name with encryption produced many extended files |
PSQL-3258 | PCC is repeating index columns when viewing indexes in SQL view |
PSQL-3276 | OLEDB application may crash when inserting SQL_BINARY data into a NOTE column |
PSQL-3289 | UNION ALL query returns more records than expected when index is used for IN list restriction |
PSQL-3310 | Incorrect results re-executing query with mixed UNION/UNION ALL and TOP clause |
PSQL-3340 | Re-executing batch sql statements with dynamics parameters may return SQLBindParameter errors |
PSQL-3440 | Added support for PDAC XE8 and XE10 |
PSQL-3452 | Monitor max worker threads should show Unlimited instead of displaying a value exceeding 256 |
PSQL-3497 | Possible engine crash when dynamic parameter fails to indicate a large chunk of data as LONGVARCHAR |
PSQL-3531 | Substring did not handle arguments that referenced positions beyond the end of the string |
PSQL-3557 | Incorrect results from using ACOS() scalar function when column is indexed |
PSQL-3576 | SQLProcedureColumns does not return default value for UDF functions. |
PSQL-3590 | Possible crash when dropping a database when another database exists that points to same location |
PSQL-3604 | Incorrect results from ADO.NET when executing stored procedure with a select into a temporary table followed by a select query |
PSQL-3622 | Query Plan Viewer chops strings inside filter window |
PSQL-3633 | Create database sql command created unneeded windows folder when using shift-jis character in folder name |
PSQL-3659 | PSQL engine stopped responding when executing select query with excessive predicates |
PSQL-3663 | PSQL engine does not ignore ? inside quotes when followed by comment marker inside the quotes |
PSQL-3665 | “Maximum number of sort columns exceeded” error is possible when using forward-only cursor |
PSQL-3702 | SQL Engine reports Memory Allocation Error on SELECT query with many OR predicates |
PSQL-3720 | Message to close Notification Viewer is confusing in cluster environment |
PSQL-3723 | Possible crash in w3odbc.dll when PARC is enabled |
PSQL-3829 | ADO.NET 4.1 provider sending incorrect parameter set to server when query has multiple statements with parameters passed in ANSI mode |
PSQL-3858 | Nested subquery returns syntax error |
PSQL-3866 | Uninstall hangs if the PSQL services are set to manual and stopped before uninstalling |
PSQL-3867 | SRDE allows multiple users into the database when setting security on database |
PSQL-3913 | Client64 installed on WGE environment corrupts ADO.NET machine.config file when updates are apply to it. |
Previous issues addressed since PSQL v11 SP3 (11.30) release:
Tracking Number | Description |
N/A | ADO.NET Provider version 4.1 added |
56790 | Repair RI database name feature added to PCC |
59978 | Query should not be re-executed when returning to a SQL Window in PCC |
60430 | Possible corruption with page compression and heavy load during continuous operations |
60600 | GUI Rebuild does not use the selected page size |
61616 | Status 1 returned on End Transaction operation when Version call is made inside transaction |
61668 | Random crash in the client cache engine |
61773 | Status 5 when performing many concurrent transactional inserts on a multi-core machine |
61765 | Correct Windows certificates on pre-Windows 8/2012 operating systems |
61808 | Status 3/73/170/171 may be seen when many users access an RI-bound database over a long time |
61820 | Engine may crash during shutdown while releasing resources |
61830 | General Error returned from a query with an outer join containing a constant value in the select list |
61836 | Problem with psp_indexes() function may cause indexes to be created with duplicate column entries |
61856 | SQL engine may crash on parameterized query with a SELECT list column name containing a ‘?’ |
61881 | Various customer-requested enhancements to the new Monitor in PCC |
61882 | PCC may hang when opening a SQL script file with many comments containing double-byte characters |
61928 | VSS Freeze stage may never complete if an EndTransaction was in progress |
61933 | LIKE with multiple wildcards may not find all matching rows |
61941 | Various display fixes & enhancements in Capacity Usage Viewer |
61953 | EOF or Syntax Error creating a Function which contains CASE via PCC |
61954 | Function Executor does not create file with non-sequential key numbers specified |
61955 | Function Executor KeyNum list does not include all key numbers for a file with non-sequential keys |
61958 | Added support for STDEVP group aggregate (Standard Deviation of a Population) |
61964 | Added support for VAR & VARP group aggregates (Variance of a Population) |
61965 | Added support for DATEFROMPARTS, TIMEFROMPARTS, DATETIMEFROMPARTS, and DATETIMEOFFSETFROMPARTS scalar functions |
61967 | SQL Engine deadlock when running with DX |
61971 | SELECT DISTINCT query with joined tables may not return distinct values |
61972 | Legacy tables not working properly with ADO.NET Entity Framework |
61975 | Invalid Column Definition error when accessing a stored view in PSQL from a linked server connection in MS SQLServer |
61978 | General Error returned on parameterized Select …WHERE ? BETWEEN column1 AND column2 |
61985 | File name in key buffer gets truncated when embedded spaces=On and file name contains multi-byte characters |
61993 | Incorrect results or SQL engine crash from REVERSE() on binary data on a Japanese OS |
62007 | ODBC application may crash when run locally on a server whose name contains Japanese characters |
62013 | PCC Server Monitor does not delete active sessions |
62014 | Various fixes to DATEFROMPARTS, TIMEFROMPARTS, DATETIMEFROMPARTS, DATETIMEOFFSETFROMPARTS scalar functions |
62020 | New Monitor does not show Japanese datasource or client host names on the SQL Active Sessions screen |
62022 | Error message truncated or not returned when calling a stored procedure with an invalid parameter |
62023 | Added status code 117 to be returned when corruption in a delta file is detected |
62024 | Function Executor list of recent files opened may not be correctly maintained |
62041 | NullPointerException error may be returned in PCC when viewing table properties |
62043 | ORDER BY an aliased column in a table subquery returns Error in Expression |
62045 | Possible Access Violation in SQL Server when using a Linked Server to PSQL |
62047 | Status 3 returned when reading a corrupt file instead of Status 2 |
62052 | Workgroup Engine failing to autoload on first open request |
62059 | Add IPv6 support for Linux |
62060 | Add IPv6 support for PDAC and OLEDB |
62061 | Add IPv6 support to pvdbpass and pvddl command line utilities |
62069 | Incorrect results from query with multiple instances of the same alias |
62072 | Incorrect results returned when calling DATETIMEOFFSETFROMPARTS with Fractions parameters set to 0 |
62074 | Count_Big() aggregate function added |
62075 | Status 12 possible on multi-core machine running multiple Btrieve applications |
62093 | Delete Session functionality of Monitor is not removing sessions |
62094 | OLEDB application connecting via IPv6 is using multiple licenses |
62097 | Status 3012 on first call to Workgroup Engine because it fails to autoload |
62109 | Possible engine crash when opening a database that has a large number of data paths defined |
62119 | User defined function is returning cached results instead of re-querying the database |
62129 | Possible SQL Engine crash when using ALTER TABLE to add an IDENTITY column on a large file |
62131 | Engine may crash when applying updates if “Accept Remote Requests” is off |
62151 | Possible status 85 in a Windows 2012 Cluster environment |
62155 | SQL engine returns incorrect results when query optimizes on a true null column’s index |
62158 | User Defined Function returns no padding spaces for fixed length strings |
62161 | Install build 024 for patch required original install files in order to complete |
62164 | Possible incorrect data used when modifying a DBMemo (longvarchar) via PDAC |
62173 | New Monitor & DTI do not properly handle Japanese machine names |
62178 | Trace requesters intermix results from different threads |
62179 | Possible segmentation fault when accessing a database through PHP using a web browser |
62180 | Workgroup engine may return status 2 opening empty data file using 512 page size on a Win2008 machine with a 4K block size |
62181 | LEFT & RIGHT scalar functions may not return correct results for binary data |
62184 | Error -3390 was returned when attempting to drop a database you have a session with, even if you are the only user with a session |
62197 | Unexpected deadlock when user is selecting on a primary key in a legacy table while another user in inserting into that table |
62202 | Slow down may be seen when license validation is executing |
62209 | The ClientWait perfmon counter was not properly decrementing |
62210 | L2 Cache size may be calculated incorrectly |
62237 | Possible status 54 and/or engine hang from Update Chunk operation following an Update |
62239 | Possible status 88 when ending continuous operations |
62253 | Double values may lose precision in ODBC applications |
62262 | Scale is missing when casting to Currency data type |
62263 | Multiple executions of cached stored procedure that has UNION or UNION ALL may not execute correctly |
62267 | Incorrect results when re-execution of query with UNION or UNION ALL |
62268 | ADO.NET provider may use an additional license on a Vista machine |
62277 | SQL engine may crash or return error when inserting a row with a LongVarBinary column populated via a SELECT |
62278 | Incorrect results when re-executing a table query with both union & union all |
62289 | Inserting and updating a binary column with an integer value produces different values |
62293 | SQL OR optimization no longer requires columns to be specified in the same order as the index |
62298 | SQL engine returns “currency not on record” instead of status 82 |
62299 | JDBC returns error or incorrect results on SELECT with subquery |
62307 | SELECT with UNION and mismatched data types may return “Numeric value out of range” |
62310 | MS Access 2013 64-bit may crash when connecting |
62313 | ALTER TABLE to change a BINARY to VARCHAR does not properly transform the data |
62315 | Added support for double-byte database names to Repair RI Database Name feature |
62323 | Increased the limit to 5000 for the maximum number of databases open at one time (64-bit only) |
62324 | PCC option to add data file to database not showing browse/ellipsis option on Japanese OS |
62326 | Possible engine crash when creating a table via ODBC using very long paths; now path can be 1024 bytes |
62337 | Precision error from SELECT with DISTINCT on a decimal column when using OLEDB |
62338 | 11.30 engine may crash when executing SELECT INTO <temp table> |
62339 | SELECT with UNION between bigint and ubigint returns SQL_ERROR -1 |
62443 | ADO.NET PSQLException only has the SQLSTATE Property set if SRDE’s SQLSTATE property is set to numeric |
62344 | SELECT with UNION between longvarchar and numeric returns SQL_ERROR -1 |
62346 | Temp tables may not all get deleted after connection is closed |
62347 | PSQL OLEDB memory leak |
62352 | ALTER TABLE from legacy NOTE/LVAR to char/varchar corrupts data and may crash engine |
62355 | "Invalid Index Name; index not found" on INSERT with JOINed subselect using named index |
62356 | Incorrect Xf$Flags values for new tables created in V2 Metadata database |
62358 | License Self Repair may fail when BackupAgent, DataExchange or AuditMaster is installed. |
62359 | Possible engine crash if block comment indicator “/*” is used in a string constant |
62360 | CREATE TABLE with column DEFAULT specifying a UDF fails if UDF doesn't exist yet |
62361 | Inconsistent upper/lower case results when fetching view names via catalog function dbo.fsqltables |
62367 | "Not authorized to perform the operation" may be returned when calling a stored procedure created with ‘Execute as Master’ |
62368 | CREATE TABLE IN DICTIONARY with USING index number clause fails if the data file doesn't exist |
62369 | Syntax error from ADO.NET provider if statement has a semicolon at the end |
62371 | Added support for PDAC XE4 and XE5 |
62373 | Possible crash when stored procedure has typo in table name |
62377 | Patch may not install over a custom installation of PSQL v11 SP3 |
62379 | Oledb not handling terminal service ID correctly, could cause crash |
62386 | Setting the Client DSN Array Buffer Size to 64 disables the buffer |
62387 | SQLBulkOperations() inserts incorrect data when auto translation is enabled and a non-default code page is in use |
62388 | Incorrect data inserted using arrays of parameters with auto translation |
62391 | Incorrect results may be returned from a Stored Procedure containing a SELECT with GROUP BY |
62393 | BUTIL –STAT using URI format (btrv:///demodata?dbfile=file.ddf) may cause the engine to hang |
62405 | Fixed length strings may not be returned correctly when concatenated in a stored procedure or function |
62408 | Engine crash when running stored procedure that use clob field. |
62411 | The client id had all zeroes in the PARC timeout messages |
62413 | Triggers may not properly handle LONGVARCHAR/NOTE/LVAR data |
62416 | Concatenating LongVarChar data in stored procedure not being handled correctly |
67617 | Possible engine crash with key inserts into file with compressed pages and several indexes |
62421 | Incorrect date return with stored procedure using UDF and ORDER BY DESC |
62422 | SQLBindCol() + SQLFetch of longvarchar data does not return all the data |
62423 | SQLGETData for multichunk data returns incorrect results for UTF8 database with auto translation |
62425 | Alter table to change default to shorter value doesn’t set value correctly |
62427 | ADO.NET batch statement not executing all statements |
62429 | Possible hang on engine shutdown |
62431 | Alter Table can change data type of Primary Key |
62432 | Update trigger may crashes with recursive updates on CLOB column |
62433 | Possible memory overrun when calling a Stored Procedure with UDF and view |
62439 | Engine crash with an update trigger on longvarchar field |
62440 | Stored procedure with group by may crash Engine when result set contains only 1 row. |
Added Support for XE6 PDAC | |
62442 | SQL LIKE operator does not work properly on strings with private characters |
62448 | Possible engine crash with very large query exceeding 64k in length |
62450 | SQL Catalog function DBO.FSQLSTATISTICS does not return all unique indexes |
62450 | PDAC does not accept decimals with commas as decimal separators |
62451 | General Error returned from Stored Procedure instead of actual error when message is too long |
62453 | 64-bit Microsoft Word crashes with ODBC DSN Connection on Windows 8 and Server 2012 |
62458 | UNION ALL on LONGVARCHAR returns incorrect results |
62459 | PSQLDataAdapter does not work with Japanese named tables |
62460 | Excel 2013 64bit crashes on loading DSN with MSDASQL |
62461 | ADO.NET may lose a row from resultset when ReturnValue parameter is set |
62463 | Engine may crash creating index on large file because of a problem related to page compression |
62466 | Added Support for XE7 PDAC |
62467 | JDBC error on SQLBINDPARM or engine crash when updating LONGVARCHAR/BINARY columns in PCC grid when multiple columns of the same data type exist |
62468 | Queries using LIKE are slower in v11 SP3 than in v9 SP2 on Japanese OS. |
62469 | Incorrect first row may be returned from Stored Procedure calling SELECT with GROUP BY |
62470 | INSERT fails on table where CHAR column has DEFAULT longer than column |
62471 | IFNULL returns Expression Evaluation Error |
62472 | SQL’s temp table closes may not be handled properly by the MKDE engine in some cases |
62473 | Random PDAC access violation errors using TPVQuery to retrieve data |
62474 | Possible crash on query containing parameterized value if incorrectly resolved. |
62475 | System.Access.ViolationException seen on ADODB.RecordSetClass.Move with dynamic cursor |
62477 | Application using CP1250 encoding with ADO.NET 4.1 does not return data. |
62478 | Stored Procedure returns incorrect results with ADO.NET 4.0, 4.2 and “invalid cast” error with 4.1 |
62480 | “Null not Valid” returned from view which has an UDF. |
PSQL-1998 | Possible status 3’s during validation process using defrag rebuild |
PSQL-2247 | ActiveX application crashes when opening file on non-existent drive mapping |
PSQL-2275 | Fujitsu Cobol ODBC sample is not working correctly with Psql ODBC |
PSQL-2279 | SQL query not executed in PCC because of single quotes |
PSQL-2285 | PVSW.Log has excessive messages, “the system cache will be used for file” |
PSQL-2287 | Data truncation error on Select statement with GROUP BY on LONGVARCHAR column |
PSQL-2297 | Constraint in Create statement does not create index |
PSQL-2298 | Cross Join query with table subquery may crash database engine |
PSQL-2327 | Memory leak in PDAC TPVQuery on table with LONGVARCHAR or NOTE field. |
PSQL-2330 | Problems with create table or create procedure column defaults |
PSQL-2350 | ISQL on Linux does not display all characters when run against Windows server. |
PSQL-2397 | Deleting database name on bound database was deleting the ddfs |
PSQL-2414 | SQL Engine crash with query including a User Defined Function that returned many rows |
PSQL-2449 | Problem using ODBC translation dll under Psql v12 |
PSQL-2473 | Bind/unbind v2 metadata returns "General_Error" |
PSQL-2548 | JCL error 3103 when URI contains Domain\\username |
PSQL-2570 | Decimal precision not handled properly in some cases |
PSQL-2571 | CAST decimal value as CHAR should maintain 0 place holders |
PSQL-2576 | Memory in use by V11.31.071 PSQL server may increase when opening and closing 1000s of files |
PSQL-2629 | Possible crashes from jdbc multithreaded application when one thread closes file while second thread is still fetching records |
PSQL-2632 | Possible crash rebuilding large segmented file into single segment file using file maintenance |
PSQL-2635 | Incompatible types in expression error after creating an index on one of the columns in the query.in ODBC application |
PSQL-2638 | Repair Bound database is not padding the Database Name with spaces |
PSQL-2643 | IFNULL/ISNULL() in other scalar functions causes "Expression evaluation error" |
PSQL-2677 | Multiple triggers on same table are not respecting execution ORDER specified |
PSQL-2960 | IndexoutOfRange exception returned by PSQL ADO.NET 4.0 and 4.1 providers. |
PSQL-2725 | ADO.Net returns “incompatible types in expression” after creating an index on one of the columns in the query |
PSQL-2774 | SQL statement is not returning the right results with ANSI_PADDING=off with temp table |
PSQL-2789 | ADO.NET fails with random error if there are nested datareaders |
PSQL-3018 | Currency Not On Record error returned with Case expression in WHERE clause |
PSQL-3020 | Currency Not on Record error with ORDER BY on temp table with Case Expression |
PSQL-3036 | File corruption may be seen in file with page compression after running rebuild |
PSQL-3042 | Underscore (_) in name cause other table records to show in table properties |
PSQL-3045 | Create Database SQL statement with blanks in the DDF or Data path causes errors |
PSQL-3046 | SRDE should create paths that do not exist when used in CREATE DATABASE |
PSQL-3051 | Use <dbname>; statement fails due to trailing semicolon |
PSQL-3052 | Select from view with UNION and invalid ORDER BY may crash the engine |
PSQL-3110 | ADO.NET 4.1 provider: INOUT is not working with Command.Text |
PSQL-3177 | CREATE TABLE with USING clause specifying a path that does not exist should create the necessary folders and the file |
PSQL-3178 | CREATE…IN DICTIONARY…USING should succeed even if the specified file cannot be opened |
PSQL-3215 | ADO.Net application is not returning the record count correctly with Global table |
Specific issues addressed in Patch release (Build 11.21.022):
Tracking Number | Description |
61808 | Status 73, 170, or 171 after engine runs for a very long time without restarting |
61845 | ADO.NET Provider returns “Unknown error -17” |
61882 | PCC may hang when opening a SQL script file with many comments containing double-byte characters |
61915 | Syntax Error from CASE expression in an UPDATE… SET clause in a stored procedure |
61918 | Invalid messages in PVSW.LOG & Notification Viewer displaying 0 sessions and/or 0 data capacity |
Previous issues addressed since PSQL v11 SP2 (11.20) release:
Tracking Number | Description |
58653 | ODBC can only retrieve up to 64K blob |
60104 | Microkernel may hang when processing a cascade delete |
60683 | ADO.NET sample “Escapes” raises “Unhandled Exception” |
60700 | Using PCC to open a table in a new window causes PCC to lose the tree view of engines and databases |
61323 | SELECT … INTO :X without a FROM clause fails in a user defined function |
61342 | ADO.NET “Communication Link Failure” with LONGVARCHAR column |
61360 | Linux client SQL application shows as user “Unknown” in Monitor |
61367 | SELECT with joins and CASE containing LIKE expression may crash the engine |
61386 | MAX and MIN aggregates on an Identity column return NULL instead of actual value |
61389 | Trigger with invalid record alias crashes the engine |
61391 | Update via SQLSetPos on table containing an Update Trigger may crash the engine |
61393 | Unsigned integer parameters to a stored procedure or function may return “Error in argument” |
61413 | Reading/inserting LONGVARCHAR or LONGVARBINARY may crash engine |
61414 | ADO.NET GetSchemaTable call may return IsKey value as empty |
61415 | “Numeric value out of range” or “No Argument or default value supplied” may be returned when UTINYINT or UBIGINT are parameters in a user defined function. |
61418 | SQL application using DAO runs slower due to limited catalog caching |
61433 | First Terminal Server session may use 2 licenses on Linux |
61439 | ALTER TABLE to RENAME the table should return an error if table has relational integrity constraints |
61441 | Accessing table with legacy “pseudo-integer” (with decimal places) may crash the engine |
61442 | Nested calls to REPLACE() scalar function returns incorrect results when called in a stored procedure |
61449 | SELECT… WHERE NOT(NOT… may return incorrect results |
61461 | SET ROWCOUNT along with ODBC SQL_ROWSET_SIZE returns incorrect results |
61463 | Data may be truncated on multiple calls to SQLBindParam and SQLExec |
61464 | JDBC is unable to resolve dynamic parameters such as: SELECT * FROM tbl WHERE ? = ? |
61478 | ODBC SQLSetStmtOption with SQL_MAX_ROWS or SQL_ATTR_MAX_ROWS returns incorrect results |
61489 | JDBC query returns no rows when using lower-case constants in restrictions on case sensitive columns |
61493 | ODBC SQLGetInfoW with SQL_INDEX_KEYWORDS was returning “Driver not capable” |
61498 | DTI function PvAddTable() is deleting the data file if an error occurs during the add |
61503 | View column alias name longer than 20 characters may cause the SQL engine to crash |
61510 | Performance issue establishing a connection when there are many (>400) active clients |
61536 | SELECT with LEFT JOIN to an empty table may cause the SQL engine to hang |
61542 | Timing window may cause possible file corruption from delta page roll-in from continuous operations |
61550 | Microkernel may hang when processing a cascade delete |
61557 | CREATE FUNCTION/PROCEDURE fails with ORDER BY clause |
61561 | “Currency not on record” returned to FORWARD-ONLY cursor on a statement using both UNION & UNION ALL along with TOP in a Table Subquery |
61565 | Status Code 7218 authorizing or de-authorizing a license on Linux |
61590 | Trigger is case sensitive for field names when referencing new and old values |
61629 | SELECT with restriction containing LEFT or RTRIM optimizing on segmented index returns too many rows |
61630 | SQL engine may crash with very large temporary sort file |
61633 | Query with UNION ALL may return too many rows when a static or dynamic cursor is used |
61646 | Update table fails via MS SQL Server linked server |
61661 | SELECT with UNION and signed/unsigned data types returns incorrect results |
61668 | Random cache engine crash may occur during page refresh |
61678 | SQL query subtracting timestamp values with ifnull() returns Expression Evaluation Error |
61683 | SQL Engine crash on query with static/dynamic cursor and partial indexes |
61689 | PCC not exporting LONGVARBINARY longer than 64KB |
61691 | DTI PvGetProductsInfo is not handling the buffer length properly |
61695 | Insert or Update of a DATE, TIME, TIMESTAMP or DATETIME with VARCHAR returns “Error in assignment” |
61697 | Engine crash with PARC enabled and re-establishing session |
61700 | SQL Engine crash on query with IN restriction using a number on DATETIME column |
61707 | Milliseconds not returned when casting a numeric value to DATETIME |
61732 | Visual Studio 2005 ADO application gets truncated VARCHAR data from a stored procedure |
61740 | Data Provider not supporting multiple active result sets correctly |
61807 | SELECT * INTO does not work across databases |
61830 | “General Error” may be returned on query with LEFT JOIN on table subqueries |
61836 | Problem with psp_indexes() function may cause indexes to be created with duplicate column entries |
61837 | Incorrect results on query requiring a temp table with computed aggregate such as max(concat(c1, c2)) |
61856 | SQL engine may crash on parameterized query with a SELECT list column name containing a ‘?’ |
Specific issues addressed in Patch release (Build 11.11.020):
Tracking Number | Description |
61433 | First Terminal Server session may use 2 licenses on Linux |
61439 | ALTER TABLE to RENAME the table should return an error if table has relational integrity constraints |
61442 | Nested calls to REPLACE() scalar function returns incorrect results when called in a stored procedure |
61449 | SELECT… WHERE NOT(NOT… may return incorrect results |
61461 | SET ROWCOUNT along with ODBC SQL_ROWSET_SIZE returns incorrect results |
61463 | Data may be truncated on multiple calls to SQLBindParam and SQLExec |
61464 | JDBC is unable to resolve dynamic parameters such as: SELECT * FROM tbl WHERE ? = ? |
61478 | ODBC SQLSetStmtOption with SQL_MAX_ROWS or SQL_ATTR_MAX_ROWS returns incorrect results |
61493 | ODBC SQLGetInfoW with SQL_INDEX_KEYWORDS was returning “Driver not capable” |
61498 | DTI function PvAddTable() is deleting the data file if an error occurs during the add |
61503 | View column alias name longer than 20 characters may cause the SQL engine to crash |
61510 | Performance issue establishing a connection when there are many (>400) active clients |
61536 | SELECT with LEFT JOIN to an empty table may cause the SQL engine to hang |
61542 | Timing window may cause possible file corruption from delta page roll-in from continuous operations |
Previous issues addressed since PSQL v11 SP1 (11.10) release:
Tracking Number | Description |
56377 | PDAC SDK install included extra files |
58653 | ODBC client cannot retrieve Blob data larger than 64K |
59542 | Function Executor does not show new COBOL datatypes |
59877 | Function Executor “View as Any Data Type” window does not show INTEGER data correctly |
60390 | SQL applications lose connection to server when PARC is enabled |
60588 | Status 3 in Windows Network Load Balancing environment (cluster) |
60597 | INSERT with SELECT failed to insert more than 2 chunks of 64k data |
60669 | Cluster name not being resolved to the host name in a 2008 R2 cluster environment |
60699 | Clilcadm -c partially removes license information before returning 7224 Lack of Permissions error |
60701 | OLEDB provider not returning Currency, Numeric or Decimal data correctly |
60748 | Create view returning message “Currency type changed” |
60746 | Stored Procedure returning message “Data truncated column 1” |
60762 | System Stored Procedure PSP_INDEXES() returns duplicate entries for Primary Keys |
60764 | Alter table doing a PHYSICAL_MOVE of BIT column puts column in wrong place |
60772 | Engine hang due to deadlock from RI |
60773 | Complicated full outer join crashes engine |
60780 | Query returns “Null not valid” if subquery contains outer join with TOP clause |
60794 | Restriction on CHAR column using UPPER() fails to find rows. |
60801 | Select into from a non-mergeable view fails |
60806 | Grant ALL on * does not include CREATESP or CREATEVIEW rights |
60811 | Adding column NOT Null constraint using existing name consumes memory |
60826 | Engine crash on SQL Query with Case Statement using constant |
60828 | Non-Master users should not be able to drop views/SP/tables created by another user. |
60857 | Currently unsupported syntax GRANT ALL on VIEW/PROCEDURE * crashes engine |
60858 | Crash in SQLDisconnect when freeing cached stored procedure statements |
60859 | SQL Engine refuses connection and status 2307 is returned |
60885 | Linux 32 bit returns numeric value out of range error |
60896 | Status 85 when using 8.3 forms of long file names like longfi~1.mkd |
60949 | Getting status 84 back is delayed ADO.NET application in client server environment |
60950 | Ability to create triggers in a secure database should require both create procedure and create table rights |
60951 | Executing a prepared statement multiple times should re-check user’s rights each time |
60957 | GRANT EXECUTE ON PROCEDURE <function name> should return an error since trusted functions are not currently supported |
60962 | Query using Btrieve temp sort file and time column not sorting correctly |
60963 | ADO.NET’s connection string Initial Command Timeout property not working. |
60966 | Memory leak in DTO retrieving dbnames information |
60977 | Stored procedure with cursor does not execute completely in some cases |
60996 | “Phantom/extra” indexes in the DDFs cause extraneous errors in PCC and DDFBuilder |
61013 | Extra index created by the SQL engine for a CREATE TABLE…IN DICTIONARY with a UNIQUE attribute specified on an Identity column |
61019 | EXECUTE of a blob variable longer than 64K in a stored procedure will cause the blob to be truncated and produce an error – most likely a Syntax Error. |
61127 | ODBC connection from client may slow down when the client machine does not have a DNS record. |
61143 | ODBC connect failed if pvTranslate=auto on Linux(32/64-bit) and 64-bit Windows |
61148 | Cancelling insert after a SetRange causes stack overflow using PDAC |
61156 | Win64 ODBC application may crash when connecting to a DSN on a Linux server with pvTranslate set to auto |
61169 | Incorrect results from query with GROUP BY on decimal column |
61172 | BUTIL crashes on Linux when doing –STARTBU with security set to “btpasswd” |
61186 | Access violation error on calculated field with PVQuery |
61200 | Query with restriction on lower() does not find matching data |
61213 | ODBC Client connection fails if the server is specified by IP address and the port number is not included in the connection string |
61228 | Query with DISTINCT, GROUP BY, ORDER BY, or UNION on a column larger than 255 bytes may be missing one or more bytes of data |
61231 | Application using multiple access methods (DTI, ODBC, Btrieve) on the same table(s) may return “Table Not Found” error |
61237 | SQL Engine crash on Linux when accessing a corrupt file with CLOB data; engine now returns status 103 |
61241 | PVNETPASS not handling the wildcard specified in quotes properly |
61253 | Incorrect results when casting binary data to integer |
61264 | Performance hit when cache engine enabled while running a SQL application that uses temporary tables |
61265 | Engine crashed when an application’s total handles exceeded 64K |
61278 | ADO.NET driver ignores a timestamp parameter if the milliseconds are non-zero |
61292 | Unable to use an IP address when opening a file with the ActiveX control |
61305 | SELECT… INTO requires a FROM clause when used in stored procedures, functions and triggers |
61306 | Intermittent ODBC connection failures with Winsock error 10065 |
61336 | Linux client receives “Could not SQLConnect” to remote Windows database |
61360 | Client application shows “Unknown” in Monitor\SQL\Active Connections for Linux client |
61367 | SELECT with joins and CASE containing LIKE expressions crashes the engine |
61386 | MAX and MIN aggregates return NULL on Identity column instead of actual value |
61389 | Engine crash when executing a trigger containing invalid syntax |
61391 | Using SQLSetPos to update a column in a table with an Update Trigger may cause the engine to crash |
61393 | “Error in Procedure argument” when calling a stored procedure or user defined function with dynamic parameters and unsigned integers |