DBGate Change History

DBGate Change History

Version 1.6, August 21, 2020

New features:

  • DBGate allows using fields of tables and views as WHERE filters.
    To create a field parameter, check the field in the field setup dialog box.
  • DBGate supports the DoNotChange handler at the object and column levels.
    You can use it to make columns read-only.
  • DBGate allows using the calendar dialog box for date parameters.
  • DBGate allows stopping the application using the /api/$stop request.
    You can use this feature when embedding DBGate to single-user applications or for development purposes.
    To enable it, set the StopEnabled option in the application settings to true.

Bug fixes:

  • DBGate raises "Object reference not set to an instance of an object" on executing MySQL procedures.

Version 1.5, August 5, 2020

Bug fixes:

  • DBGate raises "Object reference not set to an instance of an object" on executing MySQL procedures.

Version 1.4, July 31, 2020

Bug fixes:

  • A browser cannot open a page on IIS and shows the ERR_SSL_PROTOCOL_ERROR error.

Version 1.3, July 27, 2020

Improvements:

  • DBGate allows testing samples in a free version.

Version 1.2, July 24, 2020

Improvements:

  • Improved CSS and JavaScript files
  • Improved pages of samples

Bug fixes:

  • DBGate resets the selection on the right mouse button click and breaks the range copy/paste feature.
  • DBGate does not rollback cell changes when the server returns an error.
  • DBGate does not send the application/json ContentType header in several cases.
  • DBGate ignores the document base URL in API roots.

Version 1.1, July 22, 2020

New features:

  • DBGate supports copy/paste and cell range operations.
  • DBGate supports dynamic parameter values and drop-down value lists.
    For example, if a procedure has a parameter like @company_id, DBGate executes it to reload values when a user changes the company.
  • DBGate supports filtered drop-down value values.
    For example, if a value list has three columns like id, name, and item_id, DBGate filters values using the cell value in the item_id column.
  • DBGate supports JSON forms that return parameter values, column and row headers, and table cells in one JSON result.
    See the new "Sample 20 - Cube App" for details.
  • DBGate supports the /$definition operation to returns the object SQL definition.
    It returns the definition only if a user has the VIEW DEFINITION permission in a database.
    You can find a code browser sample in the DBGate samples.
  • The connection string section allows defining a default query list in the "QueryList" parameter.
    Use this feature to configure the entity container and keep the service root clear.
  • The connection string section allows defining hidden schemas in the "HiddenSchemas" parameter.
  • The DefaultValue handler allows setting default values of parameters in the HANDLER_CODE field.
  • The DoNotSort handler allows disabling the translation for the specified column or the entire table.
  • The DoNotTranslate handler allows disabling the translation for the specified column or the entire table.
  • The following handlers allow specifying data types of columns and parameters on unknown types:
    DataTypeBit, DataTypeBoolean, DataTypeDate, DataTypeDateTime, DataTypeDateTimeOffset,
    DataTypeDouble, DataTypeInt, DataTypeGuid, DataTypeString, and DataTypeTime.
    Use these handlers, for example, to specify data types of SQL code parameters or stored procedure columns.
  • DBGate supports database schemas in the endpoints.
    For example, /edit/mssql/xls27/ returns the objects of the xls27 schema with database names
    while /edit/mssql/xls27/en-GB/ returns the objects with translated names and the en-GB culture.

Improvements:

  • DBGate includes a new set of pages with complete descriptions of DBGate samples.
  • DBGate JavaScript client includes a lot of improvements.
    It has the same look in Chrome, Firefox, Opera, Safari, IE, and Edge.
    It has new classes and element ids to style DBGate elements.
  • DBGate keeps parameter values with the same name but changed ids.
    For example, the Budget item can have different ids for different companies.
    When a user changes the company_id, DBGate keeps the Budget item as a parameter.

Bug fixes:

  • DBGate allows saving changes for objects that have the merge operations only (not supported in DBGate).
  • DBGate does not translate checkbox parameter names.

Version 1.0, May 15, 2020