If you have to use MySQL / MariaDB because you have an existing project then I feel sorry for you. If you are starting a new project you should consider PostgreSQL instead. It's much smaller (a third the size on TCL) and much more standard SQL compliant. I have a few decades of Oracle DBA experience, so I think I know how a database should work. I tried MariaDB for a few weeks and quickly learned that was a bad choice. I don't use it for many of the same reasons I don't use Windows. The reason I switched to 64-bit is so that the database server can use more than 4 GB of RAM. Of course if you don't have that much memory then it doesn't matter, but if you ever want to upgrade from 32-bit to 64-bit later the data structures are different so it would be a migration effort. Just some things to keep in mind.
Thanks for the input andyj
Considering what you've said I'll look into PostgreSQL.
I've been given the task of creating a clock in/out app for volunteer, and work for the dole participants at our non profit community centre. The app has to record the time and take the persons picture as they clock in and out. The current idea is to run this from a web browser, on a tablet mounted to the wall, and the browser will store activity in a database.
I have no idea how I'm going to do this, but will start out with a simple form and database table and work my way up from there. Adding features along the way as I learn.