On 06/10/2015 03:28 PM, Samuel Debionne wrote:
> Thank you for your thoroughful answers !
>
> Following your advices, I have split XCreate and xConnect
> implementations, the first enforces the existence of the resource while
> the later returns SQLITE_OK even if the resource is missing.
>
>> The p
Thank you for your thoroughful answers !
Following your advices, I have split XCreate and xConnect
implementations, the first enforces the existence of the resource while
the later returns SQLITE_OK even if the resource is missing.
> The proper place to implement handling a missing backing storag
ation wise.
-Urspr?ngliche Nachricht-
Von: Samuel Debionne [mailto:samuel.debionne at ujf-grenoble.fr]
Gesendet: Mittwoch, 10. Juni 2015 10:28
An: General Discussion of SQLite Database
Betreff: Re: [sqlite] DROP statement on Virtual Tables
Thank you for your thoroughful answers !
Foll
>-Urspr?ngliche Nachricht-
>Von: James K. Lowden [mailto:jklowden at schemamania.org]
>On Tue, 9 Jun 2015 15:13:47 +
>Hick Gunter wrote:
>
>> xConnect is called whenever SQLite decides it needs to do something
>> with the existing virtual table. There must have been a successful
>> x
On 06/09/2015 04:46 PM, Samuel Debionne wrote:
> Hello,
>
> AFAIU, when executing a drop statement on a virtual table, the XConnect
> callback is executed first, then XDestroy.
>
> Now I have the following scenario where my virtual table is related to a
> file (say a CSV file):
>
> 1. Create the vi
treff: [sqlite] DROP statement on Virtual Tables
Hello,
AFAIU, when executing a drop statement on a virtual table, the XConnect
callback is executed first, then XDestroy.
Now I have the following scenario where my virtual table is related to a file
(say a CSV file):
1. Create the virtual table
2.
On Tue, 9 Jun 2015 15:13:47 +
Hick Gunter wrote:
> xConnect is called whenever SQLite decides it needs to do something
> with the existing virtual table. There must have been a successful
> xCreate call (in another session, another thread or another process)
> before. xConnect is not allowed
Hello,
AFAIU, when executing a drop statement on a virtual table, the XConnect
callback is executed first, then XDestroy.
Now I have the following scenario where my virtual table is related to a
file (say a CSV file):
1. Create the virtual table
2. Delete the CSV file from disk
3. Try to drop th
8 matches
Mail list logo