Discussing the article: "Market Simulation (Part 21): First Steps with SQL (IV)"
Write more just don't ruminate, it's time to move on to the second step, the first steps are too long.
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Check out the new article: Market Simulation (Part 21): First Steps with SQL (IV).
Hello and welcome to another article in the series about the replication/simulation system.
In the previous article “ Market Simulation (Part 20): First steps with SQL (III)” we talked a little about the SELECT command. We need to look at one more concept in order to use SQL more effectively or, more precisely, so that we can take advantage of everything SQL does. This is a better alternative than programming an application that would perform the same work, namely maintaining databases and allowing us to manipulate them. This other concept is key when it comes to databases. We are talking about keys, which can be either primary keys or foreign keys.
But although MetaEditor allows us to perform tasks with SQLite, if you are just starting out and want to learn how to work with SQL more consistently, you will need a more sophisticated tool. One important point: I am not saying that MetaEditor is not functional. But MetaEditor is not suitable for understanding some things. This is because its purpose is different, namely editing and compiling code written in MQL5. The substantial help it provides us in using SQLite is not enough for what we really need when it comes to learning.
Therefore, in this case, I will allow myself to suggest another tool. This is because it is actually oriented toward working with SQLite. Although, using MySQL or any other platform for working with SQL, in practice we will get the same result. As we made clear in previous articles, it does not matter which system we use to access SQL. All of them will be able to do the same thing, provided, of course, that we use only and exclusively SQL syntax, without resorting to anything that exists only in that specific variety of SQL.
Author: Daniel Jose