2 ms·
I was surprised to see SQLite listed as a source but not as a destination. Any big reasons for that or is it just something you haven't got around to implementi
by simonw 3y ago
I was surprised to see SQLite listed as a source but not as a destination. Any big reasons for that or is it just something you haven't got around to implementing yet?
I've been getting a huge amount of useful work done over the past few years sucking data from other systems into SQLite files on my own computer - I even have my own small db-to-sqlite tool for this (built on top of SQLAlchemy) - https://github.com/simonw/db-to-sqlite https://github.com/simonw/db-to-sqlite
- xk3 3y agoI used sqlite-utils to create a tool that can merge SQLITE files and split them: https://github.com/chapmanjacobd/library?tab=readme-ov-file#organize-via-separate-databases https://github.com/chapmanjacobd/library?tab=readme-ov-file#...
- karakanb 3y agoI do use the dlt library to support as many source & destinations as possible and they do not support SQLite as of today. I am interested in supporting SQLite simply because I love it as well, so that's definitely in the roadmap. db-to-sqlite looks lovely, I'll see if I can learn a thing or two from it!
- mritchie712 3y agolooks like dlt doesn't support it as a destination (which this is a wrapper around) https://dlthub.com/docs/dlt-ecosystem/destinations/ https://dlthub.com/docs/dlt-ecosystem/destinations/
- MatthausK 3y agoone of the dltHub founders here - we aim to address this in the coming weeks
- MatthausK 3y agoone of the dltHub founders here - we aim to address this in the coming weeks