Saving Data

SaveToDB products enable saving changes in two scenarios:

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

This section focuses on configuring methods for the Save button.

For details on the second scenario, refer to Change Handlers.

You can implement saving changes to a database in four ways:

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 leverage these methods to configure REST API for POST, PUT, and DELETE operations.

For more information, see:

• Saving Data via DBGate
• Saving Data via ODataDB

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

For further details, check out:

• Saving Data Using OData
• Saving Data Using REST API

Additionally, the SaveToDB add-in supports merging data.

Explore these advanced features as well:

• Saving Data Using JSON
• Saving Formulas and Comments
• Disabling Saving Data

Configuration Tables and Views

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

Here’s a sample of the xls.objects table:

Here’s a sample of a query list view:

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

Use query list views to create automatic configurations using SQL.

To utilize 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.

Most topics in this section provide samples for the xls.objects table.