| Section | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
One advantage to using version v2.5 of the Database Connector with v7.2.1 is that the configuration.xml is separated from the underlying infrastructure database and related credentials. Review the enhancements below for more reasons to upgrade.
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.
...