> On Jul 14, 2019, at 10:05 AM, ardi wrote:
>
> Do you have any recommendation for saving the inmemory db in a safe
> way?
If you’re going to keep your data in memory, there’s no good reason to use
SQLite at all. Just define custom model objects that you can operate on
efficiently, and write
On July 15, 2019 12:01:00 a.m. EDT, "J. King" wrote:
>On July 14, 2019 11:56:15 p.m. EDT, Donald Shepherd
> wrote:
>>Somewhat bizarrely only "BLOB" affinity doesn't make it from the
>>original
>>table to the new table when using the "select" syntax to create the
>new
>>table. Even items with
On July 14, 2019 11:56:15 p.m. EDT, Donald Shepherd
wrote:
>Somewhat bizarrely only "BLOB" affinity doesn't make it from the
>original
>table to the new table when using the "select" syntax to create the new
>table. Even items with aliased affinities (VARTEXT, or something that
>defaults to
Somewhat bizarrely only "BLOB" affinity doesn't make it from the original
table to the new table when using the "select" syntax to create the new
table. Even items with aliased affinities (VARTEXT, or something that
defaults to NUMERIC) comes across as the base affinity but at least have an
On 14 Jul 2019, at 6:05pm, ardi wrote:
> I have read the backup API page (https://www.sqlite.org/backup.html)
> that shows how to read a sqlite db from disk to memory, and how to
> save it back to disk, but it doesn't talk about the topic of
> performing the save in a safe way.
This is a
Hi!
I'm going to use sqlite as means of the file format I/O for
applications. One of the critical points in file I/O is saving the
file in a safe way, so that data loss cannot happen (or at least the
risk of happening is minimized as much as possible). Traditionally,
some applications save their
On 14 Jul 2019, at 11:18am, Chaoji Li wrote:
> This problem is only present for 3.28+. A sample test case is attached.
Thank you for identifying this behaviour. I'm sure the development team will
reply to your post.
Attachments are automatically ignored by the mailing list. You can include
This problem is only present for 3.28+. A sample test case is attached.
Basically, the flow is:
1. Open in-memory db A (we don't do anything about it).
2. Open db B from file test.db
3. Create a blob handle from B
4. close_v2 A
5. close_v2 B
6. close blob handle -> Segmentation fault
The
Hi,
In reply to
https://www.mail-archive.com/sqlite-users@mailinglists.sqlite.org/msg113512.html.
Can you please accept this patch?
Thanks,
- Orgad
This email and any files transmitted with it are confidential material. They
are intended solely for the use of the designated individual or
9 matches
Mail list logo
