This documentation is for Live Forms 7.3 Not for you? Earlier documentation is available too.

Skip to end of metadata
  • Created by Former user, last modified by Former user on Oct 24, 2017
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

Review the database connector compatibility release matrix for your Live Forms version. Click to download the Database Connector.

Database ConnectorLive Forms
v2.5.3v7.3.2+
v2.5.21v7.2.x2
v2.4 Any version prior to v7.2.0

  1. 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.

  2. 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.

v2.5.3 (r31018)

10/TBD/2017

The Database Connector can be deployed in any servlet container i.e.tomcat or in Standalone mode. This release contains enhancements and bug fixes. You can download it from here.

Enhancements:

  • #21523 - Database connector version annotation added to generated XSDs to help manage xsd changes
  • #21549 - Errors for certain CRUD operations return an error to the frevvo forms server. THe submission repository will flag the submission with an error icon. The tenant admin or any designated flow admins receive email alerts.    
  • #21643 - New Property to create error logs in JSON format
  • #21665 - Log Database and Driver version and revision numbers
  • #21714 - Database Connector version/revision added to status page

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' to return an empty string for databse columns that have blank or null values
  • #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

v2.5.2 (r30569)

7/28/2017

The Database Connector can be deployed in any servlet container i.e.tomcat or in Standalone mode.

Tickets Fixed:

  • #21139 - A third party JDBC driver to connect to Active Directory as an SQL database causes validation to fail. Drivers of this type are not supported
  • #21150 - Adding SQL Server JDBC driver to WAR causing issues for customers who already have the driver installed in the tomcat/lib directory
  • #21156 - MS SQL JDBC driver embedded in the dbconnector causing queries to not work after upgrading to version 2.5 of the Database Connector
  • #21196 - Write dbconnector logs to tomcat/logs/database-connector.YYYY-MM-dd.log instead of frevvo.log    
  • #21232 - jTDS driver does not work with DBConnector v2.5.0
  • #21279 - Log is not generated when configuration parameters are located in database.xml 

  • #21411 - <cache/> element in configuration.xml causing error

  • #21421 - Autocreate="true" does not work"

  • #21428 - Empty resultsets report "Document is null. Premature end of file" errors in the debug console when testing forms  

v2.5.0 (r29937)

4/29/2017

The Database Connector can be deployed in any servlet container i.e.tomcat or in Standalone mode.

Enhancements:

  • #18166 - Batch processing of POST/Create requests. JDBC inserts are batched instead of performing individual inserts.
  • Logging improvements
  • KIOSK mode - when no configuration.xml is defined, the KIOSK mode pre-loads BIRT (ClassicModels) and myStore QuerySets with in-memory Derby databases. This will make it very easy to try out the DB Connector.
  • #19243 - Support for JSON payload from business rules when performing POSTs and PUTs.
  • #20546 - Query statements are validated when the DB Connector starts instead of when used.
  • Console prints the DB Connector version and revision number.
  • #18620 - Generating max-length for SQL Server NVARCHAR
  • #20532 - Ability to disable QuerySets and/or Querys while developing your integration.
  • #18708, #18676 - Returns blank or null in the JSON results for columns that have blank or null values..
  • The database.war is  executable - there is the option to either deploy the WAR in an existing Servlet Container or simply run the WAR in standalone mode (with java -jar dbconnector.war).
  • The SQL Server JDBC driver is included in the Database connector war.
  • QuerySet and Query names only allow alphanumeric, dot, dash and underline characters. They must start with letters. This change makes sure that they are automatically XML and JSON friendly.
  • The driver and validationQuery attributes in <resource-def> are now optional: they will be properly inferred based on the current database.
  • The configuration.xml file is automatically picked up from the current directory where the DB Connector was launched or from ./config/configuration.xml. It can be manually set by using the frevvo.connectors.database.configuration property as before. This is specially useful when running the DB Connector standalone.
  • #9564 - Ability to generate schemas for all queries in a queryset. This makes it possible to download a single XSD for all queries at once.

Tickets Fixed:

  • #19062 - MySQL column w/ timestamp datatype failing when trying to insert date/time control value.
  • #9244  -  http.post() to DB connector not working from rules for URL parameters and JSON payload in POST/PUT requests.
  • #9565  -  A query with '<' sign in it does not work.
  • #12750 - DB Connector:Support PUT/POST for European Characters.
  • #13134 - Database POST fails when there is % character in one of the fields.
  • #18620 - SQLSERVER : Datatype nvarchar does not generate max-length restrictions   
  • #18207 - Errors while inserting, updating, selecting row(s) using the DB connector are simply logged and ignored: it always returns an HTTP 200 status code.

v2.4

6/22/14

This version is a rebuild and has the same content as the v2.3.1 connector.

v2.3.1 (r20198)

3/18/2013

  • Retrieved data can now be cached by the connector for improved performance.
  • Status Url database/status returns current configuration information
  • All database operations now log start/stop time and a WARN if time exceeds a configured threshold
  • Using prepared statements to execute all queries for enhanced security
  • #4638 Improved logging message make diagnosing and solving database issues faster/easier.
  • #6532 Values passed to the connector that contain Url special characters such as '&' cause value truncation
  • #8123 POST Url paramenters were ignored when there was no XML document sent also
  • #8693 Status 500 returned when sending a delete request
  • #8705 Query to update same form fields twice and 2nd time returned row has NULL in one of the columns, value on form is not cleared. Old value from 1st query remained.
  • #8906 DB column NOT NULL but with a default value should not be required in the auto generated XSD schema
  • #6605 Errors are logged as INFO when they should be WARN or ERROR

v2.2 (r10466)

10/20/09

  • #4515 - Update is no longer run after autocreate Insert. Not needed
  • #4798 - Warn if deleteKey does not exist in the schema returned by the retrieve statement
  • #5485 - UTF-8 characters retrieved from DB causing MalformedByteSequenceException in connector

v2.1 (r9567)

7/9/09

  • #1466 - Column names with underscore characters sig1_name='{sig1_name}' not getting template replaced
  • #5026 - readme is out of date
  • #4648 - _mediaType=json returns JSON rather than the default XML

v2.0 (r8967)

5/7/09

  • Datasource definitions delegated to the container and are resolved by the connector through JNDI lookup. The resource reference is configured in the connector configuration file.
  • A single database connector instance can work with multiple databases.
  • Execute stored procedures. If the stored procedure does not have OUT parameters it is not necessary to declare the statement as a procedure.
  • It is possible to configure all Date and timestamp formats for both the database and the generated XML.
  • Hot update of the configuration file. The connector will pick up the changes within 5 seconds.
  • Parameters passed in the URL take precedence over values provided in the body of POST and PUT requests. Useful for  rules.
  • Multiple statements. It is possible to execute multiple SQL statements for one URL. This is available for the "create", "update" and "delete" operations. The retrieve operation only allow one statement.

v1.0

GA Release

  • No labels