Versions Compared

Key

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

...

Note the string {customerId}. The database connector SQL statements are actually templates that are resolved at run time using values passed in the http request. In the example above, if there is a parameter in the http GET request that hits the connector with customerId=1234 than the statement would return the record for customer 1234.

Support for NULL or Blank Values

By default, optional/empty form fields will send a null from the form field to the Db Connector and return an xml element or json property for an optional/empty form field when the database column contains a null. This is controlled by the emit Null column feature.

...

There are two ways to disable the emit null Null column feature:

  1. Add the dbconnector.emitNullColumns=false property to the dbconnector properties file for your installation.

  2. OR add the emitNullColumns="false" attribute to the respective element in the configuration.xml file for your installation:

    For example:

  • To disable it at the instance level add the attribute at the top of configuration.xml

    Code Block
    <dbconnector version="2.5" emitNullColumns="false">
  • To disable it at the queryset level, add the attribute to the respective queryset in configuration.xml

    Code Block
    queryset name="BIRT" emitNullColumns="false">
  • To disable it at the query level, add the attribute to the respective query in configuration.xml

    Code Block
    <query name="lkadgroupmembers2" emitNullColumns="false">

...