rs-bounces at mailinglists.sqlite.org
[mailto:sqlite-users-bounces at mailinglists.sqlite.org] Im Auftrag von Steve
Schow
Gesendet: Mittwoch, 11. Mai 2016 17:04
An: SQLite mailing list
Betreff: Re: [sqlite] 2 different SQLite versions inside the same process space
Ok?starting to s
On 5/11/16, Steve Schow wrote:
>
> Typically concurrency happens when two different users execute their program
> that has sqlite compiled into it;?.. concurrently.
The problem only comes up with two different copies of SQLite are
running within the same process. The same program being run
Ok?starting to sound safer. :-)
at a minimum this problem only occurs when multi-threading is being used to
access a sqlite DB file. but I think its probably even more specific then that?
When you say ?two copies of sqlite in the same address space?, this is the part
I am getting confused
On 10/05/16 23:43, Dominique Devienne wrote:
> That explains how to avoid symbol mixups, to have two or more SQLite
> "instances"
> in a single process, but doesn't address the concern about POSIX locks
> DRH mentioned.
> if more than one of those same-process instances access the same file. --DD
On Wed, May 11, 2016 at 4:16 AM, Roger Binns wrote:
> On 10/05/16 10:42, Andrey Gorbachev wrote:
>> I am a bit worried that the initialisation of 2 different versions of SQLite
>> would interfere with one another. Any advice?
>
> There is a way to do it, [...] create a .c file that near the top
On May 11, 2016, at 8:22 AM, Steve Schow wrote:
>
> Oh that actually makes more sense?but also even more concerning in a way,
> unless I?m still misunderstanding the conundrum.
Just thinking out loud?.is this problem related to specifically when people try
to compile sqlite into a shared
On May 10, 2016, at 4:15 PM, Richard Hipp wrote:
> On Tue, 10 May 2016 22:47 +0100, Tim Streater wrote:
>>
>> I read it as two different *copies*. It doesn't sound to me as if the
>> versions have anything to do with it.
>>
>
> Correct. Two different *copies*of the library. They can both
On 10 May 2016, at 10:29pm, Steve Schow wrote:
> are you saying that on UNIX, if two different versions of the sqlite3 binary
> attempt to access a DB file at the same time?then the globals that are used
> in the sqlite3 binaries related to locking may be different in the two
> different
On 10 May 2016 at 22:29, Steve Schow wrote:
> I would like to understand this issue a little bit better?
> On May 10, 2016, at 2:31 PM, Richard Hipp wrote:
>>
>> In unix, SQLite has to use global variables to work around the
>> well-known design bugs in posix advisory locks. And so if you
On 10/05/16 10:42, Andrey Gorbachev wrote:
> I am a bit worried that the initialisation of 2 different versions of SQLite
> would interfere with one another. Any advice?
There is a way to do it, and I use it for my Python APSW extension as
the recommended build instructions. It is especially
Hi,
Microsoft Excel allows custom "Addins", which are all run in the same process
space. We use Bloomberg Excel Addin, which uses SQLite 3.7.x and we have no
control over what version of SQLite they use. We have our own Addin which uses
SQLite 3.11.x and we do not want to use the same version
On Tue, 10 May 2016 22:47 +0100, Tim Streater wrote:
>
> I read it as two different *copies*. It doesn't sound to me as if the
> versions have anything to do with it.
>
Correct. Two different *copies*of the library. They can both have
the same version number - that doesn't matter.
--
D.
On 5/10/16, Andrey Gorbachev wrote:
> Hi,
>
> Microsoft Excel allows custom "Addins", which are all run in the same
> process space. We use Bloomberg Excel Addin, which uses SQLite 3.7.x and we
> have no control over what version of SQLite they use. We have our own Addin
> which uses SQLite
I would like to understand this issue a little bit better?
On May 10, 2016, at 2:31 PM, Richard Hipp wrote:
>
> In unix, SQLite has to use global variables to work around the
> well-known design bugs in posix advisory locks. And so if you have
> two different instances of SQLite running on
IF you have two different versions of SQLite linked into the same
executable, both accessing the same database, then the problem that
the globals work around can happen. It won't happen if different
processes use different versions of SQLite (say two versions of the
sqlite3 binary, or sqlite3
15 matches
Mail list logo
