I'm thinking of trying to implement this but just wanted to put up an issue for comments and feedback from the community and to see if anyone else had an interest in contributing!
SQLite is a performant flat-file database that's often touted as the "zero-config" database - you can even run it entirely in memory in your program! Python's standard library already includes a SQLite connector, meaning the addition of a SQLite Parsons database connector should add no additional dependencies to the library.
Detailed Description
There should be a SQLite database connector with full parity (to the extent that the SQLite library allows, there are some limitations) with other database connectors.
Context
Parsons already exposes functionality to export tables as CSVs for longterm storage, but SQLite could fill a gap where an analysis might involve multiple tables or be too complicated or large for CSVs to be practical, but setting up a whole database would be overly burdensome or not necessary.
I'm thinking of trying to implement this but just wanted to put up an issue for comments and feedback from the community and to see if anyone else had an interest in contributing!
SQLite is a performant flat-file database that's often touted as the "zero-config" database - you can even run it entirely in memory in your program! Python's standard library already includes a SQLite connector, meaning the addition of a SQLite Parsons database connector should add no additional dependencies to the library.
Detailed Description
There should be a SQLite database connector with full parity (to the extent that the SQLite library allows, there are some limitations) with other database connectors.
Context
Parsons already exposes functionality to export tables as CSVs for longterm storage, but SQLite could fill a gap where an analysis might involve multiple tables or be too complicated or large for CSVs to be practical, but setting up a whole database would be overly burdensome or not necessary.
Priority
Low Priority