My sqlite-utils library has evolved to the point where I think it would make a good foundation for the next version of csvs-to-sqlite.
The main feature I'm excited about here is being able to handle giant CSV files - right now they have to be loaded into memory by Pandas, but sqlite-utils has similar functionality which handles them as streams, reducing the amount of memory needed to consume a huge file.
I intend to keep as much of the CLI API the same for the new version, but this is a big change so it's likely some cases will break. As such, I intend to keep the 1.x branch around (and maintained with bug fixes) for users who find that 2.0 doesn't work for them.
I'll pin this issue for a few weeks so people can comment on this plan before I start executing.
My sqlite-utils library has evolved to the point where I think it would make a good foundation for the next version of
csvs-to-sqlite.The main feature I'm excited about here is being able to handle giant CSV files - right now they have to be loaded into memory by Pandas, but sqlite-utils has similar functionality which handles them as streams, reducing the amount of memory needed to consume a huge file.
I intend to keep as much of the CLI API the same for the new version, but this is a big change so it's likely some cases will break. As such, I intend to keep the
1.xbranch around (and maintained with bug fixes) for users who find that 2.0 doesn't work for them.I'll pin this issue for a few weeks so people can comment on this plan before I start executing.