Saving Data to Views

Saving Data to Views

To save changes to a view, specify the target view using INSERT, UPDATE, and DELETE objects.

Example: xls.objects Table

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

IDTABLE_SCHEMATABLE_NAMETABLE_TYPETABLE_CODEINSERT_OBJECTUPDATE_OBJECTDELETE_OBJECT
 s02view_cashbookVIEWs02.view_cashbooks02.view_cashbooks02.view_cashbook
 s02usp_cashbookPROCEDUREs02.view_cashbooks02.view_cashbooks02.view_cashbook
 s02code_cashbookCODE<SQL>s02.view_cashbooks02.view_cashbooks02.view_cashbook

Example: QueryList View

Here’s a sample from the QueryList view:

IDTABLE_SCHEMATABLE_NAMETABLE_TYPETABLE_CODEINSERT_PROCEDUREUPDATE_PROCEDUREDELETE_PROCEDUREPROCEDURE_TYPE
 s02view_cashbookVIEWs02.view_cashbooks02.view_cashbooks02.view_cashbook
 s02usp_cashbookPROCEDUREs02.view_cashbooks02.view_cashbooks02.view_cashbook
 s02code_cashbookCODE<SQL>s02.view_cashbooks02.view_cashbooks02.view_cashbook

Tools like SaveToDB 8+, DBEdit, DBGate, and ODataDB automatically create these configurations if the target view is detected and is updatable.

For instance, if a user has the VIEW DEFINITION permission and a view or stored procedure contains code like SELECT * FROM s02.view_cashbook, the system can identify the target view.

Keep in mind that target views must be updatable and contain primary key or identity columns.

Implementation Details

SaveToDB and DBEdit generate and execute INSERT, UPDATE, and DELETE commands automatically.

DBGate executes INSERT, UPDATE, and DELETE commands on the server-side based on POST, PUT, and DELETE requests.

ODataDB creates EntitySets for views and FunctionImports for stored procedures and SQL codes targeting the appropriate EntitySet.

This website is using cookies. By continuing to browse, you give us your consent to our use of cookies as explained in our Cookie Policy.