Hello. Which database is the easiest way for a newbie to work in C ++? I worked with Access on C #, but now this DBMS is forbidden, so an alternative is needed ... The following types of queries are planned: sampling, updating, deleting, adding the maximum that will be complicated - interaction with two tables at once. The topic of connecting to the selected DBMS is especially important. I tried to work with MySQL, but since My RAD Studio XE8 compiled only applications in 32-bit format, the ODBC driver did not want to work correctly (windows 64 bit, so I downloaded the appropriate driver) and I had a lot of errors. I would like to avoid such problems. So, what can you advise?)
Closed due to the fact that it is necessary to reformulate the question so that it was possible to give an objectively correct answer by the participants Harry , αλεχολυτ , D-side , rjhdby , rdorn 14 Mar '17 at 21:33 .
The question gives rise to endless debates and discussions based not on knowledge, but on opinions. To get an answer, rephrase your question so that it can be given an unambiguously correct answer, or delete the question altogether. If the question can be reformulated according to the rules set out in the certificate , edit it .
- oneSQLite than not good? - avp
- onePostgreSQL is good for everyone :-) - Eugene Bartosh
- LibreOffice Base :-) - Sergey
- Would advise SQLite. Easy, does not require any external DBMS. It is quite functional. Of course, she has simplified reduced opportunities, but for 90% of the tasks they have enough of them. Used by many quite serious software, by the way. - Harry
- Is it possible to interact with SQLite? - Andrey Fedorov
1 answer
First of all, you need to determine for what purposes the DBMS is required.
If the base is needed for convenient local storage of any internal settings, data or states, the best option, as suggested by the SQLite commentators.
I would only advise you to take, for example, a sqlite3pp wrapper in order to write C ++ code, not C. And the connection can only be importing a header file, which can be a huge plus.
If the future is a server application, then MySQL (based on ambiguity of requirements is the best option), and working with it using the mysql ++ wrapper.