Schema Modeler for Windows

From RemObjects Wiki
Jump to: navigation, search

This is a Tool topic for Data Abstract


NOTE: This is article is a work in progress and not finished yet.
Unless you are the author, please do not make changes or rely yet on information presented in this article.

When done, the author should change the first line from wip to wipr to show that the page is ready for review.

If you have suggestions for this page, please send them to us: email.

General Overview

Schemas are one of the powerful features of Data Abstract, used to abstract the structure and type of the back-end database away from the code in the client and middle tier, as described in more detail here. Schema Modeler™ 7 for Windows is a tool for defining and maintaining of Data Abstract schemas. It was created to replace an old version of modeler application, to provide us with better flexibility moving forward and be able to maintain new Data Abstract features.

Schema Modeler 7 for Windows.png


Schema Modeler™ has been designed from the ground up to be usable both by developers for implementing the middle (and possibly client) tier, as well as database administrators or architects that only want to define the schemas that later will be coded against by other members of the development team. It is integrated with the Visual Studio and Delphi IDEs, but can also be used standalone by running it from the Windows Start menu or by double-clicking a .daSchema file in Windows Explorer. You also can start Schema Modeler™ with additional options from command line, using command line arguments.

Tasks typically performed in Schema Modeler™ include:

  • Define Connections against the real back-end databases, using any of the many drivers supported by Data Abstract.
  • Browse tables, views and stored procedures available on the back-ends, with Connection Manager.
  • Define Data Tables and other schema objects to expose as part of the schema, via drag and drop from Connection Manager or by manually configuring the tables as desired.
  • Where needed, configure Column Mappings to define how fields from data tables map to differently-named fields in the back-end.
  • Configure mappings of data tables to differently-named tables in the back-end databases, when targeting multi-database scenarios.
  • Run and test data tables against various back-ends to see if they are functioning as expected.
  • Define Business Rules scripts for Data Tables, Commands and the whole Schema, using smart javascript editor.

You can find more information here:

See Also


Product: RemObjects Data Abstract
Available Editions: Data Abstract for .NET, Xcode, Delphi, Java and JavaScript

GlossaryArticlesFeaturesLibrarySamples