ODataDB Change History

Version 3.8, August 21, 2020

New features:

• ODataDB allows using fields of tables and views as WHERE filters.
  To create a field parameter, check the field in the field setup dialog box.
• ODataDB creates functions for handlers that select data from tables and views and have specified columns in the HANDLER_CODE.
  For example, if the handler selects values from the s02.companies table and has a value like "id,+name",
  ODataDB creates the s02_companies_select_id_name_order_by_name function that select id and name and sorts data by name.
  For the value like "id,+name,@item_id", ODataDB creates a function like s02_companies_select_id_name_where_item_id_order_by_name.
• ODataDB supports the DoNotChange handler at the object and column levels.
  You can use it to make columns read-only.
• ODataDB allows using the calendar dialog box for date parameters.
• ODataDB allows stopping the application using the /v4/$stop request.
  You can use this feature when embedding ODataDB to single-user applications or for development purposes.
  To enable it, set the StopEnabled option in the application settings to true.

Improvements:

• ODataDB supports the odata.include-annotations=* and odata.include-annotations=-* options of the Prefer header.
  Also, ODataDB has a new IncludeAnnotations configuration option that allows defining the default option of including annotations to the metadata.
• ODataDB supports the odata.metadata=none option of the Accept header.
• ODataDB hides columns of unsupported data types in metadata and does not select such columns.
• ODataDB marks function result types with the OpenType attribute.
• ODataDB replaces dots and dashes in database object names with _x002E_ and _x002D_ to avoid issues with URLs and parameters.
• Metadata contains ODataDB.DisplayName values in the Annotation nodes with PropertyPath attributes.

Bug fixes:

• Microsoft PowerQuery cannot load ODataDB feeds due to metadata errors.
  Note that PowerPivot cannot load JSON feeds anyway. Use PowerQuery to load data.
• ODataDB metadata contains the Annotations nodes in the EntityType nodes that do not follow the standard.
  Such nodes are moved to the Schema node.
• ODataDB metadata uses the wrong Boolean words in several nodes instead of the correct Bool.
• ODataDB returns DateTimeOffset values for Date type columns in JSON feeds.
• ODataDB does not return the content type for metadata and service documents.
• ODataDB does not generate the ROWNUM pseudo-primary key column for views in MySQL, Oracle, and DB2.
• ODataDB has issues with schemas in SQLite.
• ODataDB has broken the @odata.context value for URLs that include cultures.
• The odatadb-control CSS has an issue with overflow.

Version 3.7, August 5, 2020

Bug fixes:

• ODataDB does not return the entity when the return=representation header specified.
• ODataDB raises "Object reference not set to an instance of an object" on executing MySQL procedures.

Version 3.6, July 31, 2020

Bug fixes:

• A browser cannot open a page on IIS and shows the ERR_SSL_PROTOCOL_ERROR error.
• The client returns "Incorrect syntax near ')'" on saving changes.
• The server does not save changes of data from stored procedures to base tables.

Version 3.5, July 27, 2020

Improvements:

• ODataDB allows testing samples in a free version.

Version 3.4, July 24, 2020

Improvements:

• Improved CSS and JavaScript files
• Improved pages of samples

Bug fixes:

• ODataDB resets the selection on the right mouse button click and breaks the range copy/paste feature.
• ODataDB does not send the application/json ContentType header in several cases.
• ODataDB ignores the document base URL in API roots.

Version 3.3, July 22, 2020

New features:

• ODataDB supports copy/paste and cell range operations.
• ODataDB supports dynamic parameter values and drop-down value lists.
  For example, if a procedure has a parameter like @company_id, ODataDB executes it to reload values when a user changes the company.
• ODataDB supports filtered drop-down value values.
  For example, if a value list has three columns like id, name, and item_id, ODataDB filters values using the cell value in the item_id column.
• ODataDB 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.
• ODataDB supports the non-OData standard /$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 ODataDB 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 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.
• ODataDB 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:

• ODataDB includes a new set of pages with complete descriptions of ODataDB samples.
• ODataDB 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 ODataDB elements.
• ODataDB data service always creates derived EntityTypes for results of stored procedures adding the _result suffix.
  For example, if a dbo.usp_cashbook procedure has the code like SELECT * FROM dbo.cashbook, ODataDB creates the usp_cashbook_result EntityType with the cashbook base type.
  This change makes the model consistent with all types of procedures.
• ODataDB data service includes improvements in detecting and creating navigation properties.
• ODataDB 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, ODataDB keeps the Budget item as a parameter.

Bug fixes:

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

Version 3.2, May 15, 2020

Improvements:

• ODataDB migrated to ASP.NET Core 3.1.
• ODataDB supports installing as a Windows service.
  Use install-odatadb-service.cmd to install it.
• The JavaScript client has several minor improvements.

Bug fixes:

• Fixed bug with a connection using SQLite ODBC drivers

Version 3.1, February 28, 2020

New features:

• The JavaScript client supports conditional formatting specified with the Format handlers in the xls.handlers table.
• The JavaScript client uses xls.formats table formats to hide hidden columns loaded for the first time.
• The JavaScript client allows sorting columns.
• The data service supports the /$table_format suffix and returns table formats defined with the Format handlers in the xls.handlers table.
• The data service supports the /$excel_format suffix and returns Excel table formats defined in the xls.formats table saved using the SaveToDB add-in.

Improvements:

• The JavaScript client shows parameters of the bit and boolean datatypes as three-state checkboxes.

Version 3.0, December 12, 2019

New features:

• ODataDB is an ASP.NET Core 3.0 application.
• ODataDB includes a JavaScript client that allows viewing and editing data.
• ODataDB supports Windows, Linux, and Mac OS.
• ODataDB supports views and stored procedures.
• ODataDB supports SaveToDB Framework.
• ODataDB includes a new command-line product activation tool.

Removed Features:

• Support of OData-Atom
• Support of OData 1.0-3.0
• Support of Microsoft SQL Server Compact