Use the right database for the job. Databases tend to be grouped into Relational (SQL: MySQL, MariaDB, Postgres) and Non-Relational (NoSQL: MongoDB, CouchDB, Redis) databases. SQL databases work well for well structured data that can be normalized. NoSQL databases manifest in different forms such as key/value store, document based, or graph based. All are geared towards different use cases and present advantages and disadvantages. I'm partial to SQL databases because I was exposed to them first.
You may be able to use CSV to store your values if they are not complex. There is also sqlite.
Late last night I started trying MySQL, and I like it! Some of the table set up is confusing, such as how to make it so that new records have their primary key auto-incremented.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Use the right database for the job. Databases tend to be grouped into Relational (SQL: MySQL, MariaDB, Postgres) and Non-Relational (NoSQL: MongoDB, CouchDB, Redis) databases. SQL databases work well for well structured data that can be normalized. NoSQL databases manifest in different forms such as key/value store, document based, or graph based. All are geared towards different use cases and present advantages and disadvantages. I'm partial to SQL databases because I was exposed to them first.
You may be able to use CSV to store your values if they are not complex. There is also sqlite.
Late last night I started trying MySQL, and I like it! Some of the table set up is confusing, such as how to make it so that new records have their primary key auto-incremented.