Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #197773
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | “How to back up SQLite databases the right way (not by copying them!)” |
| Date | 2026-05-10 22:36 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <10tr1ab$n8tt$1@dont-email.me> (permalink) |
Mr Serdar Yegulalp occasionlly comes up with useful titbits of information, but I’m not sure I’d count this among them <https://www.infoworld.com/video/4164431/how-to-back-up-sqlite-databases-the-right-way-not-by-copying-them.html>. Does anybody else use SQLite’s backup API? I’ve never bothered, because SQLite is a single-user DBMS. To backup a database, I just shut down the program accessing it, and do a regular file copy on the database file. Simple. I think the backup API might be useful from within the app accessing the database itself, to provide its own backup function while it is still running. Again, not something I’ve felt much need for; in my experience, long-running service-style apps tend to use multiuser DBMSes, which can handle multiple simultaneous connections without things getting confused. And backing them up is easily done by making yet another connection from a database dump utility, usually provided as part of the DBMS package.
Back to comp.lang.python | Previous | Next — Next in thread | Find similar
“How to back up SQLite databases the right way (not by copying them!)” Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-05-10 22:36 +0000 Re: “How to back up SQLite databases the right way (not by copying them!)” Jon Ribbens <jon+usenet@unequivocal.eu> - 2026-05-10 23:09 +0000
csiph-web