The overall goal for stat-log-db (at the time of writing this) is to make a GUI for viewing (and managing?) log data created by a 3rd-party software (that uses stat-log-db). This means that stat-log-db needs a database to hold the log data in, and a way to easily interface with that database.
Ideally stat-log-db will provide python classes representing the Database and other database-related concepts, e.g. Connections, Cursors, etc. These classes and their relationships constitute "Database Interface Architecture" (at least for this ticket. Those words could mean other things in other contexts, even within this project.).
The overall goal for stat-log-db (at the time of writing this) is to make a GUI for viewing (and managing?) log data created by a 3rd-party software (that uses stat-log-db). This means that stat-log-db needs a database to hold the log data in, and a way to easily interface with that database.
Ideally stat-log-db will provide python classes representing the Database and other database-related concepts, e.g. Connections, Cursors, etc. These classes and their relationships constitute "Database Interface Architecture" (at least for this ticket. Those words could mean other things in other contexts, even within this project.).