Saving Data
Special offer: 50% discount ($1440) for ODataDB Enterprise until May 31, 2024

Saving Data

SaveToDB products allow saving changes in two events:

  1. When a user clicks the Save button
  2. When a user changes a cell

This section describes configuring methods for the Save button.

To learn about the second way, see Change Handlers.

There are four ways to implement saving changes to a database:

  1. Saving changes to a table
  2. Saving changes to a view
  3. Saving changes using stored procedures
  4. Saving changes using SQL

SaveToDB and DBEdit execute SQL commands against the database connection.

DBGate and ODataDB use these methods to configure REST API for POST, PUT, and DELETE operations.

See details in the following topics:

The SaveToDB add-in supports saving changes for OData and REST API data services.

See details in the following topics:

The SaveToDB add-in also supports merging data.

Take a look at the following advanced features also:

Configuration Tables and Views

You can configure saving changes in the xls.objects table or via query list views.

Here is a sample of the xls.objects table:

IDTABLE_SCHEMATABLE_NAMETABLE_TYPETABLE_CODEINSERT_OBJECTUPDATE_OBJECTDELETE_OBJECT
 s02usp_cashbookPROCEDUREs02.cashbooks02.cashbooks02.cashbook

Here is a sample of a query list view:

IDTABLE_SCHEMATABLE_NAMETABLE_TYPETABLE_CODEINSERT_PROCEDUREUPDATE_PROCEDUREDELETE_PROCEDUREPROCEDURE_TYPE
 s02usp_cashbookPROCEDUREs02.cashbooks02.cashbooks02.cashbook

Use the xls.objects table to configure the default behavior.

Use the query list views to create automatic configurations using SQL.

To use a query list, SaveToDB and DBEdit users must select it in the Connection Wizard dialog box.

DBGate and ODataDB support query lists via URL segments or settings in the configuration files.

Topics of this section usually show samples for the xls.objects table.