Discussion of article "SQLite: Native handling of SQL databases in MQL5" - page 4
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
A very detailed tutorial on SQLite: https://www.sqlitetutorial.net/
Here's one on SELECT: https://www.sqlitetutorial.net/sqlite-select/
There is no sense to transfer it to our help and there is a lot of detailed documentation published for this project.
Most likely, we will include direct links to ready tutorials in our help.
SQL is a language, albeit a simple one, and there are a lot of textbooks on it, including in Russian. It is inefficient to learn the language from documentation/reference books.
SQL is a language, albeit a simple one, and there are a lot of textbooks on it, including in Russian. It is inefficient to learn the language from documentation/reference books.
To some people. Personally, I find documentation like in MQL5 more pleasant than examples of use. I started programming in Wasik using similar documentation.
Added: I have searched, read textbooks in Russian.... Tough. People without thinking copy machine translation without reading. V.S. Vysotsky "They don't care what flowers are there."
It is impossible to learn anything from such translations ...
A very detailed tutorial on SQLite: https://www.sqlitetutorial.net/
Here's one on SELECT: https://www.sqlitetutorial.net/sqlite-select/
There is no point in moving it to our help and there is a lot of detailed documentation published for this project.
Most likely, we will include direct links to ready tutorials in our help.
After a closer, but still superficial, familiarisation with the possibilities of SQLite I came to the conclusion that in this form, sorry, it is only a rattle.
In order to use the unconditional advantages of SQLite it would not be superfluous to have a history database, at least. And better, a database of current positions and pending orders. I hope that at the MT level the creation of such databases will not take much time. Especially if the tables, as they are now, can be formed from SQLite database. This approach will definitely simplify the work with the history of orders and deals. It will be very easy to get the amounts of swap, commissions, profit on all deals with one position ID or for a certain period.
Recently I read in one of the topics that the history selection is based on the opening time, but correctly on the closing time.... Having a SQLite database removes such questions. By what criterion you want to use and select it. But few programmers will create these bases for themselves. IMHO.
To some people. Personally, I find MQL5 documentation more pleasant than examples of use. I started programming in Wasik using similar documentation.
Added: I searched, read the tutorials in Russian.... Tough. People without thinking copy machine translation without reading. V.S. Vysotsky "They deeply do not care what flowers there."
It is impossible to learn anything from such translations ...
"Hey."
After a closer, but still superficial, familiarisation with the capabilities of SQLite, I came to the conclusion that in this form, sorry, it is only a rattle.
In order to use the unconditional advantages of SQLite it would not be superfluous to have a history database, at least. And better, a database of current positions and pending orders. I hope that at the MT level the creation of such databases will not take much time. Especially if the tables, as they are now, can be formed from SQLite database. This approach will definitely simplify the work with the history of orders and deals. It will be very easy to get the amounts of swap, commissions, profit on all deals with one position ID or for a certain period.
Recently I read in one of the topics that the history selection is based on the opening time, but correctly on the closing time.... Having a SQLite database removes such questions. By what criterion you want to use and select it. But few programmers will create these bases for themselves. IMHO.
There already is. By means of MQL. You know where. But you say you can't read more than three sentences....
"Her."
In this case, a minor paraphrase is not important.
It already is. By means of MQL. You know where. But you say you can't read more than three sentences....
I don't get it. I don't know where it is. What do you mean, "With MQL tools"? As it is now possible to pull and pull from a SQLite database is a very big difference. Even after a superficial acquaintance it is clear. By means of MQL is much more complicated and, as it seems to me, more costly in time.
When it is written on the matter without unnecessary empty phrases, I can read a little more. This article is written in such a way.
In this case, minor paraphrasing is not important.
I don't understand anything. I don't know where it is. What do you mean by "MQL tools"? As it is now possible to pull and pull from a SQLite database is a very big difference. Even after a superficial acquaintance it is clear. By means of MQL is much more difficult and, as it seems to me, more costly in time.
When it is written on the matter without unnecessary empty phrases, I can read a little more. This article is written in such a way.
I've long ago made it possible for that data sampling you mentioned. It works for both platforms. And it's described in the articles. It's been done a long time ago. It will be further refined, but later. I don't want to discuss here what is not relevant to this topic.
I've long ago made it possible for that data sampling you mentioned. It works for both platforms. And it's described in the articles. It's been done for a long time. It will be further refined, but later. I don't want to discuss here what is not relevant to this topic.
Exactly. Artem, you have done it with MQL, but the topic is about SQLite. Even your library would be simpler and more "high-speed" if it used SQLite databases. I was not talking about the absence or impossibility of doing it. I was talking about the simplicity of the solution.