I agree with wavic on sqlite3. I use either sqlite3 or PostgreSQL on all of my projects,
sqlite3 is prefect when you need to redistribute because it's all in one file.
However, (I realize your not there yet, just tuck this info away for now) should you consider
at some point in the future something more robust, then investigate PostgreSQL.
During my career, we had to keep data for (when you combined landline, cellular and fiber -- now, Century Link (then called QWest)),
we had to deal with over 100 million customers.
I was a decision maker, and I would not have considered MySQL, but most certainly would PostgreSQL.
I'm done.
sqlite3 is prefect when you need to redistribute because it's all in one file.
However, (I realize your not there yet, just tuck this info away for now) should you consider
at some point in the future something more robust, then investigate PostgreSQL.
During my career, we had to keep data for (when you combined landline, cellular and fiber -- now, Century Link (then called QWest)),
we had to deal with over 100 million customers.
I was a decision maker, and I would not have considered MySQL, but most certainly would PostgreSQL.
I'm done.