Versions Compared

Old Version 11

changes.mady.by.user Former user

Saved on

compared with

New Version 12

changes.mady.by.user Former user

Saved on

Key

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

This page contains release notes for the  Database Connector.

...

One advantage to using version v2.5 of the Database Connector with v7.2 is that the configuration.xml is separated from the underlying infrastructure database and related credentials. SYSADMINS can change database hosts, usernames, passwords without touching the configuration.xml. The configuration file can be stored without security risks. Review the enhancements below for more reasons to upgrade.

Enhancements:

  • #18166 - Batch processing of POST/Create requests. JDBC inserts are now 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 - JSON payload now supported 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 WAR is now 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 now open source and included in the WAR
  • QuerySet and Query names only allow alphanumeric, dot, dash, and underline characters and it can only start with letters - this 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.
  • #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    

v2.4

6/22/14

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

...