Discussing the article: "Market Simulation (Part 22): Getting Started with SQL (V)"

[MetaQuotes]

Check out the new article: Market Simulation (Part 22): Getting Started with SQL (V).

Before you give up and decide to abandon learning SQL, allow me to remind you, dear readers, that here we are still using only the most basic elements. We have not yet looked at some of SQL's capabilities. Once you understand them, you will see that SQL is far more practical than it seems. Although, most likely, we will eventually change the direction of what we are building, because the creation process is dynamic. We will show a little more about creating different things in SQL, because this is truly important and useful for you. Simply thinking that you are more capable than an entire community of programmers and developers will only lead to wasted time and opportunities. Do not worry, because what comes next will be even more interesting.

In the previous article “Market Simulation (Part 21): First Steps in SQL (IV)”, we explained, in an abstract form, how a relational database can be separated from a non-relational one. But, first of all (and this was the reason for writing the previous article), we tried to show how the working principle of a database can be understood. This was done so that you could understand that, although it may seem reasonable to program certain things, in some cases an existing implementation can be used to achieve the expected result in an application.

This is precisely why we are spending time explaining SQL instead of programming in MQL5. We need to even things out a little so that everyone can understand why we will use SQL when we could create routines and more routines to build some implementation.

In this case, the implementation will allow us to develop a suitable and simple way for the replication/simulation system to have a command system. That is, we need some way to store the order and position system in order to carry out studies in the replication/simulation system. In my opinion, creating many routines for this is completely unnecessary, since MQL5 allows us to use certain SQL support through SQLite. But for those who are eager to keep creating code after code, we will show a better alternative. This is because the time that would be spent implementing, testing, and configuring procedures to create some kind of database can be used more productively on other matters.

Author: Daniel Jose