3 ms·
> I do exactly the same with traditional RDMS. For the use case of "I need a quick database for some ad hoc analysis", SQLite has a lot less friction than a tr
by skissane 6y ago
> I do exactly the same with traditional RDMS.
For the use case of "I need a quick database for some ad hoc analysis", SQLite has a lot less friction than a traditional RDBMS. Creating a new DB, backing it up, sharing it with others – all these tasks are doable on a traditional RDBMS too, but generally involve additional steps or prerequisites compared to what SQLite requires.
> Export to single file isn't nothing new.
Most databases have some kind of export/import function based around CSV, SQL, XML, JSON, or even some proprietary binary format.
But SQLite is a lot easier than that – I can just copy a single database file to another system and just open it and it works straight away. (The only proviso is make sure the DB isn't open at the time of copy, to avoid any corruption issues.) No need to run some time consuming import/export process which converts between the external format and the database's native storage format.
- pjmlp 6y agoSame here, depending on the project, I always have either SQL Developer with Oracle, or SQL Server Management Studio with SQL Server installed.
- skissane 6y agoCopying a database to another machine is a lot simpler with sqlite than with either of the tools you mention. So I don't agree with the "same here" part.