Previous versions' tutorials (obsolete)
/tutorials/version-3-x-tutorialsThis section contains the tutorials that we written for older versions of EasyQuery and most probably are obsolete now.
Aggregate data
/tutorials/aggregate-dataFrom this article you will see how to aggregate (count, sum, etc.) data in your queries.
Managing data formats
/tutorials/managing-data-formatsThis article shows how to implement some particular tasks with your query
Data Model
/fundamentals/data-modelIn 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:
About Data Model Editor
/data-model-editor/aboutHere you can find detailed information about this instrument and guideline, how to use it to perform all needed tasks.
Date/time values formatting
/how-to/date-time-formattingIn this article, you can find instructions how to set up different types of date & time formats, with code examples.
Customizing SQL query formats
/how-to/customizing-sql-query-formatsDetailed instruction with various examples of how to operate with different query formats.
JavaScript widgets formats and settings (Webforms)
/tutorials/javascript-widgets-settings-formats-webformsHow to set up column formats and change default settings of the table.
Working with several data models
/tutorials/several-data-modelsAll 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)..
Possible ways of data model creation and loading
/tutorials/data-model-creation-loadingEasyQuery components need a [data model](/$aid/03bc06b0-83ec-4040-97ef-a50ca004177f) (a user-friendly representation of your DB) for their work. There are several different ways to create the model and load it on your project's startup. This article will describe all of them in detail.
Navigate through data model entities and attributes
/how-to/run-through-data-model-entitiesA code snippet which demonstrates how to run through data model entities and attributes
Building data model dynamically by DB meta-information
/how-to/build-data-model-by-db-meta-informationIt's easier to fill your model right in the code directly from your database, using meta-information
Building data model dynamically by information from a DataTable
/how-to/build-data-model-by-info-from-datatableExample of how to build data model by certain information from DataTable
Attaching extra data to a query on the client-side
/tutorials/attaching-extra-data-to-query-client-sideSometimes it's necessary to attach some extra data to each query (based on some user's input on the client-side) and then use that extra data on query execution. For example, user might want to specify a date (or a period of time) as an additional filter to the any query. To add some extra data you can use beforeExecuteQuery event handler which can be defined on view initialization: Now if you check in Developer Tools (on Network tab), each .../execute request now includes ad additional data object in the request payload. Now to process this additional request data you can create your own implementation of EasyQueryManager and override its ExecuteQueryCore method. Here is an example: Here we just reconfigure our current query and add in it an additional condition group with a bunch of conditions like SomeColumns contains 'filter text' Finally, you need to register your manager class on EasyQuery middleware initialization: NB: Please note that you can read the ClientData property in any method of your custom manager.
Adding a new operator to your data model
/tutorials/add-new-operatorHere you can find all information about how to add a new operator to your data model either using Data Model Editor (DME) or with a code
Creating data model dynamically with code
/how-to/create-data-model-dynamically-with-code-Data Model- object is an essential part of EasyQuery framework. However, sometimes you need to add some entities, entity attributes or operators to the existing model or to fill it from scratch using DB metadata information got from another source. In these cases, you can use EasyQuery API to build the model dynamically. Finally, we add entities and entity attributes. Here is an example of creatin a small data model: two tables (Customers and Orders) with one link between them, 2 entities (Customer and Order correpondingly) and a few attributes in each entity.
JavaScript widgets formats and settings (MVC version)
/tutorials/javascript-widgets-settings-formatsIn this article, we describe the most common unique settings for EasyQuery JavaScript widgets and give examples of code.
Working with data models in EasyQuery
/getting-started/working-with-data-modelThis article will guide you through all issues about working with data models in EasyQuery library. How to load it from the DbContext or from your DB connection, or now to create a new one using Data Model Editor.