Data Model Editor

About Data Model Editor

Here you can find detailed information about this instrument and guideline, how to use it to perform all needed tasks.

Data Model

In short (and by its name), data model - is a model (representation) of some data stored in your database. It solves two major problems: Presents the data to the end user in a more friendly and familiar way. Contains some meta information that helps EasyQuery components to build query statements in SQL or other query languages. Any data model contains the following main sections:

Table class

Table class represents one table in a [Korzh.EasyQuery.Db.DbModel](api-reference-4x/korzh-easyquery-db-namespace/dbmodel-class) object

Table class

Table class represents one table in a [Korzh.EasyQuery.Db.DbModel](api-reference/korzh-easyquery-db/korzh-easyquery-db-namespace/dbmodel-class) object

API reference

Table class

Table class represents one table in a [Korzh.EasyQuery.Db.DbModel](api-reference-5x/korzh-easyquery-db-namespace/dbmodel-class) object

Value Editors

Here you can find the full list of editors and choose any you need in your work with Data Model:

Korzh.EasyQuery namespace

Korzh.EasyQuery namespace

Korzh.EasyQuery.Db namespace

Korzh.EasyQuery.Db namespace

Korzh.EasyQuery namespace

Korzh.EasyQuery.Db namespace

Korzh.EasyQuery namespace

Korzh.EasyQuery

Basic classes of EasyQuery library.

API reference 4.x (obsolete)

API reference 5.x (obsolete)

Aggregate data

From this article you will see how to aggregate (count, sum, etc.) data in your queries.

Working with several data models

All EasyQuery demos works with one data model (and one database which corresponds to that model). Here we are going to describe how to add a selector that switches between two data models on your view/page and then how to setup a custom "model loader" to handle GetModel requests propertly. To make it possible to switch between these two models we need some selector element on our page. The only problem here - is to switch the database connection accordingly the the switches between the models. Now when the user selects an item in our model selector element on the client-side - our server-side code automatically loads the selected model and connects to a proper database (when necessary)..