From your description it is still unclear why you need database in the first place. If you need just some persistent storage, are you sure you need relational monster like mysql? Perhaps storing data in json-formatted text file is enough?gdillen wrote:I read already different postings about using databases on the Pi. Mainly sqlite3 is advised in most situations. What I want to achieve is that different sensors send data (of course this can happen simultaneously) to the Pi. I suppose since sqlite3 is a single user db probably its not suited for this project? What are my alternatives, that are performance wise acceptable: MySQL, ...?
simple file storage is the fastest way to store this kind of linear captured senor data.gdillen wrote:Thanks all for the info/recommendations. Maybe it was not clear for what I need a db: I want to store eg captured sensor data on my Pi.
How much data? How big is a data record? How's it keyed (date/time or something else)? What are you doing with it after it's captured?gdillen wrote:Thanks all for the info/recommendations. Maybe it was not clear for what I need a db: I want to store eg captured sensor data on my Pi.
You want to save whole videos in your database? Or only the references, and store the videos themselves somewhere in the filesystem? For the latter, any embeddded database will do. But if you want to store whole videos in the database, I'd recommend something that can work with BLOBs (Binary Large OBjects). With that, the videos themselves are not squeezed into the database structure, instead they are saved on the file system, and only the references are stored within the database structure. The database engine takes care for proper linking between these items. PostgreSQL can handle this, for example. See here for more: https://www.postgresql.org/docs/current ... jects.html