|
From: | Max Nikulin |
Subject: | Re: [PATCH] ob-sqlite: Use a transient in-memory database by default |
Date: | Sun, 7 May 2023 21:45:14 +0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 |
On 07/05/2023 03:40, Rudolf Adamkovič wrote:
SQLite shell, which defaults to in-memory for good reasons.
Explicit :memory argument still suppresses the following warning:
Connected to a transient *in-memory* *database*. Use ".open FILENAME" to reopen on a persistent database.
I am not an active sqlite user and I have never tried it from Org. However mostly I used it with files. The case for in-memory database was unit tests for python functions.
Babel allows to compute values of header arguments and I am not in favor of silently treat nil (due to e.g. a error in the called function) as disabled persistence. Ihor's idea with a warning is better from my point of view.
[Prev in Thread] | Current Thread | [Next in Thread] |