Saving Data to Views
Special offer: 50% discount ($1440) for ODataDB Enterprise until June 24, 2024

Saving Data to Views

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

Here is a sample for 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

Here is a sample for 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

SaveToDB 8+, DBEdit, DBGate, and ODataDB create such configurations automatically if the target view can be detected and the view is updatable.

For example, if a user has the VIEW DEFINITION permission and a view or stored procedure has the code like SELECT * FROM s02.view_cashbook.

Target views must be updatable and have primary key or identity columns.

Implementation Details

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

DBGate uses INSERT, UPDATE, and DELETE commands on the server-side according to POST, PUT, and DELETE commands.

ODataDB creates EntitySets for views and FunctionImports with the target EntitySet for stored procedures and SQL codes.