Lele Gaifax writes:
> Paul Moore writes:
>
>> If you were interested in doing that, I'd suggest opening a tracker issue
>> with a patch.
>
> Excellent, will do that, thank you for the encouragement!
See http://bugs.python.org/issue27645
Thank you in advance for any feedback!
ciao, lele.
--
n
Paul Moore writes:
>> Original questions still hold, though.
>
> Indeed - I don't see any reason why exposing the backup API through
> the sdlib module would be unacceptable (there's plenty of
> sqlite-specific functionality in there already, it's not as if there's
> a need to limit the module to
On 11 July 2016 at 16:59, Lele Gaifax wrote:
> Paul Moore writes:
>
>> There's also apsw (https://github.com/rogerbinns/apsw), which appears
>> to support backup - http://rogerbinns.github.io/apsw/backup.html.
>
> Thank you, will have a look: not sure it fits my need, because the application
> is
Paul Moore writes:
> There's also apsw (https://github.com/rogerbinns/apsw), which appears
> to support backup - http://rogerbinns.github.io/apsw/backup.html.
Thank you, will have a look: not sure it fits my need, because the application
is currently based on Python's sqlite module (thru SQLAlch
On 11 July 2016 at 10:51, Lele Gaifax wrote:
> as I'm going to have a need to use the native `online backup API`__ provided
> by SQLite, I looked around for existing solutions and found `sqlitebck`__.
>
> I somewhat dislike the approach taken by that 3rd party module, and I wonder
> if the API sho
Hi all,
as I'm going to have a need to use the native `online backup API`__ provided
by SQLite, I looked around for existing solutions and found `sqlitebck`__.
I somewhat dislike the approach taken by that 3rd party module, and I wonder
if the API should/could be exposed by the standard library s
