SQLExport from MDriven Server
No edit summary
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==== SQLExport ServerSide Action ====
==== SQLExport ServerSide Action ====
The SQLExport action is used to write data from your model into another external SQL database. It is an alternative way to export data, that needs no other external components or maintenance than what MDriven Server provides.
The SQLExport action is used to write data from your model into another external SQL database. It is an alternative way to export data 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 data row(s) to insert or update, and on data - 'queryforinsert','queryforupdate' and 'queryforselectcount' as attributes (if queryforselectcount returns 0 the queryforinsert is used, else update).
SQLExport requires 'connectionstring' on root, 'data' (column name must start with 'data', case insensitive) as a Nesting that contains the data row(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.''
'''''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.
The very common case of “replicating” some model-driven data to another database is implemented and scheduled in minutes.
Line 12: Line 12:
==== Common Gotchas ====
==== Common Gotchas ====
The data nesting must be collected even when you work in 1 object -> do self->asset
The data nesting must be collected even when you work in 1 object -> do self->asset
The MDriven Book - See: [[Training:OCL Expressions|OCL Expressions]]


[[Category:Advanced]]
[[Category:Advanced]]
[[Category:MDriven Server]]
[[Category:MDriven Server]]
[[Category:The MDriven Book]]
[[Category:The MDriven Book]]

Latest revision as of 05:26, 3 April 2024

SQLExport ServerSide Action

The SQLExport action is used to write data from your model into another external SQL database. It is an alternative way to export data 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 data row(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 collected even when you work in 1 object -> do self->asset

The MDriven Book - See: OCL Expressions

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