SQLite in MQL5: new features and performance testing - page 3

 
Are there plans to support a regular SQL server? It has more features.
 
Another question. Is it possible to transfer a previously saved base to RAM for fast operation. I couldn't find a function.
 
Реter Konow:
Another question. Is it possible to transfer a previously saved base to RAM for fast operation. I couldn't find a function.
Judging by the signature of the database creation function, it replicates the file function, and by this logic, the same function that creates a new one opens the saved database. So, if you pass the base creation flag to it in RAM, it will move the saved database there?
 
The question "how to edit a saved base" remains open. It would be good to have an example.
 
As I understand it, there is a special language for working with such a database. At least give me a list of keywords with brief comments. Or is it on the "take it and leave it" principle?) Not everyone has had experience with this.
 
Реter Konow:
As I understand it, there is a special language for working with such a database. At least give me a list of keywords with brief comments. Or is it on the "take it and leave it" principle?) Not everyone has had experience with this.

https://sqlite.org/lang.html

 
Maxim Dmitrievsky:

By the way... recently noticed that the laptop is slowing down. Cleaned the drive, decided to check how the ssd feels, as it's a shiny piece of hardware I haven't studied much. Checked it showed 68% remaining life, laptop is just over 2 years old. That's funny.

But as far as I remember, the screw on the spindle could have died after 2 years quietly.

System drive, all appdata/roaming files for MT5 are on another one, haven't checked that one.

The question is moot. I have 3 drives running since 2012. )))

 
That's cool. Thanks. So, a whole language to learn. Then practice for a month and go for it! But, if you really have to, why not? ))
 
Реter Konow:
Cool. Oops. So, a whole language has to be learned. Then practice for a month and go! But, if you really have to, why not? ))

The SQL language is too extensive for MQ to include in the documentation. But for simple personal purposes, the basic constructs will settle down quickly enough.

It should be understood that it is not a programming language, but a query language.

 
Edgar Akhmadeev:

The SQL language is too extensive for MQ to include in the documentation. But for simple personal purposes, the basic constructs will settle down quickly enough.

It should be understood that it is not a programming language, but a query language.

Thank you, that makes sense now.