On 12 Nov 2010, at 4:44pm, Dennis Suehr wrote:
> Firstly, a bit more background information. The system will be running on
> Linux (kernel > 2.6.0) and all accesses to the database will be via local
> disk (ext3 or similar).
This allows me to be a little more precise about my answers, I think
> However, I am surprised that it does not at least possess a
> list of all open handles to a given database. If I had that, then I could
> close all DB connections either before the delete or after. Are you sure
> that such a list does not exist?
If SQLite was able to obtain such list (not in t
Simon,
Many thanks for your prompt and thorough response.
Just a couple of follow-up questions if I may:
Firstly, a bit more background information. The system will be running on
Linux (kernel > 2.6.0) and all accesses to the database will be via local
disk (ext3 or similar).
1) I appreciate y
On 11 Nov 2010, at 4:05pm, Dennis Suehr wrote:
> I need to implement a function which will be able to delete a previously
> created database. I plan to do this by obtaining an exclusive lock to the
> DB, then closing my connection (which as I understand will still keep the DB
> locked) and then
Hello,
Apologies if an answer to my query exists elsewhere. I have been searching
for a fair while without success.
I am building an SQLite interface as a C shared library and consequently
will have no knowledge or control of concurrent connections to any databases
which are created by it.
I ne
5 matches
Mail list logo
