Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Review the database connector compatibility release matrix for your Live Forms version. 

Excerpt


Database ConnectorLive Forms
v2.6.2v9.1.x
v2.6.11v9.0.6+
v.2.6.01v9.0.x

v2.5.6

Deployed to v8.0 in cloud, v.7.4.8+ for in-house
v2.5.5v7.4.x
v2.5.44v7.4.x
v2.5.33v7.3.2+
v2.5.22v7.2.x2
v2.4 Any version prior to v7.2.0
  1. In order to run v9.0.x with the Database Connector, you must upgrade the Database Connector to v2.6.0.

  2. If you are running Database Connector v2.5.0 - v2.5.2 you must upgrade to v2.5.3+ due to issues solved in 2.5.3.

  3. In order to run the Database Connector v2.5.3 you must upgrade to  v7.3.2+. v2.5.3 was not certified with earlier versions.
  4. In order to run the Database Connector v2.5.4 you must upgrade to v7.4.x. v2.5.4 was not certified with earlier versions.

Info

frevvo only supports/certifies the Database Connector running in the Apache Tomcat container. Refer to our Supported Platforms for the list of Application Servers and databases supported/certified by frevvo.

 

Table of Contents
maxLevel1

v2.6.2 (r66bf773)

Cloud: December 14, 2019

Version 2.6.2 of the Database Connector is a small bug fix release. Cloud customers running the Database Connector on-premise can download the Database Connector Standalone zipfile or the database.war zipfile from our frevvo Software Downloads Directory. This version was deployed to the frevvo Cloud on December 14, 2019

Tickets fixed:
  • TIP-26620 - Starting frevvo v9.0 takes too long ~10 mins

v2.6.1 (r273473f)

Cloud: Oct 12, 2019

In-house:  Oct 16, 2019

Version 2.6.1 of the Database Connector is a small update release. In-house (at the time of v9.0 upgrade) and Cloud customers running the Database Connector on-premise can download the Database Connector Standalone zipfile or the database.war zipfile from our frevvo Software Downloads Directory. This version was deployed to the frevvo Cloud on October 12, 2019

v2.6.0 (red37cb0)

Cloud: Aug 17, 2019

...

  • TIP-22454 - Warning message added to Database Connector log when the connection threshold is exceeded.
Tickets fixed:
  • TIP-22161 - Property to disable query/querySets is not working (#22204)
  • TIP-22418 - HTTP Get with templatized URIs fails when control values have special characters
  • TIP-22419] - DB connector queries where parameter values are encoded using encodeURIComponent() do not work after DB Connector 2.4 -> .2.5.4 upgrade

...

  • #21859 - Add support for JAVA_OPTS in standalone database-connector (Cloud Only)

  • #21872 - Management endpoints on port 8083 (Cloud Only)

Tickets fixed:
  • #21969 - Workaround for generated schema that may not upload successfully when using copy/paste to make the xsd file in the Chrome browser.

  • #22025 - NPE when calling a Stored Procedure that does not return a resultset using a <retrieve> statement 

...

Tickets fixed:
  • #21524 - SQL queries with empty results fail with UncategorizedSQLException error
  • #21527 - HTTP Get through the Database Connector doesn't return results    
  • #21543 - emitNullColumns atrribute default value reverted to 'false'. When this attribute is set to false, the database connector will not return any xml or json value for any database column that is blank or null.
  • #21594 - DBConnector fails when query has more parameters than the columns returned
  • #21674,#21755 - DOC URL fails with "Unable to autocreate row for query" error when it hits the first empty row    
  • #21684 - MSSQL Driver not found error    
  • #21716 - NPE calling HTTP PUT from curl    
  • #21717 - Row count reported in database connector log is incorrect for create operation

...