Message304789
I'm using sqlitebck which provides similar functionality but instead of using a file name to store the backup it uses connection instances.
I find it very useful. Here is my use case: to run tests of an application that requires a database filled, I do a 'copy' of an existing sqlite backup in a ':memory:' database.
But with the proposed API, it is not possible to use the resulted ':memory:' database because it will be delete when the connection is closed.
So I propose to add the option to pass a connection instead of a filename. |
|
Date |
User |
Action |
Args |
2017-10-23 09:59:35 | ced | set | recipients:
+ ced, ghaering, r.david.murray, berker.peksag, lelit, abarry, anish.shah, palaviv |
2017-10-23 09:59:34 | ced | set | messageid: <1508752774.78.0.213398074469.issue27645@psf.upfronthosting.co.za> |
2017-10-23 09:59:34 | ced | link | issue27645 messages |
2017-10-23 09:59:34 | ced | create | |
|