SQLExport from MDriven Server
No edit summary
No edit summary
Line 9: Line 9:


[[File:Exporting files from MDriven Server 06.png|frameless|769x769px]]
[[File:Exporting files from MDriven Server 06.png|frameless|769x769px]]
==== Common gotchas ====
The data nesting must be collection even when you work in 1 object -> do self->asset
[[Category:Advanced]]
[[Category:Advanced]]
[[Category:MDriven Server]]
[[Category:MDriven Server]]

Revision as of 10:16, 18 December 2020

SQLExport serverside action

The SQLExport action is an action used to write data from your model into another external SQLdatabase. It is an alternative way to export data – a way that needs no other external components or maintenance than what MDriven Server provides.

SQLExport requires 'connectionstring' on root, 'data' (column name must start with 'data', case insensitive) as a Nesting that contains the datarow(s) to insert or update and on data - 'queryforinsert','queryforupdate' and 'queryforselectcount' as attributes (if queryforselectcount returns 0 the queryforinsert is used, else update).

Update 2018-10-18: you can now use 'connectionstringodbc' and the logic will use ODBC connection instead.

The very common case of “replicating” some model driven data to another database is implemented and scheduled in minutes.

Exporting files from MDriven Server 06.png

Common gotchas

The data nesting must be collection even when you work in 1 object -> do self->asset

This page was edited 47 days ago on 04/03/2024. What links here