On Thu, Sep 28, 2017 at 9:18 PM, Keith Medcalf wrote:
>
> If they are both using the same connection, yes. Transaction state is an
> attribute of the connection, not the statement or thread.
>
>
Thanks everybody for the explanations! I have moved to a connection per
thread model since to avoid t
On Thu, Sep 28, 2017 at 3:11 PM, Igor Korot wrote:
> Not if you use connection-per-thread model.
>
>
Yes, right. That I understand and am in the midst of doing that right now.
-aps
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http
On Thu, Sep 28, 2017 at 2:10 PM, Simon Slavin wrote:
>
>
> On 28 Sep 2017, at 6:57pm, Keith Medcalf wrote:
>
> > The mutex is used to prevent multiple concurrent entry (ie, calling an
> sqlite3_* function) using the same connection from multiple threads. (ie,
> serialization). It does not prov
On Thu, Sep 28, 2017 at 1:30 PM, Simon Slavin wrote:
>
>
> On 28 Sep 2017, at 6:16pm, pisymbol . wrote:
>
> > So even with full mutex, if I have thread 1 issue a "BEGIN" and it starts
> > processing, and another thread 2 issues a "BEGIN" somewhere in
On Thu, Sep 28, 2017 at 1:16 PM, pisymbol . wrote:
>
>
> On Thu, Sep 28, 2017 at 11:55 AM, Simon Slavin
> wrote:
>
>>
>>
>> On 28 Sep 2017, at 3:31pm, pisymbol . wrote:
>>
>> > Specificially, if thread 1 and 2 both have a handle to sqlit
On Thu, Sep 28, 2017 at 11:55 AM, Simon Slavin wrote:
>
>
> On 28 Sep 2017, at 3:31pm, pisymbol . wrote:
>
> > Specificially, if thread 1 and 2 both have a handle to sqlite3 with full
> > mutex, then both could start a transaction simultaneously, one will win
> the
Hello:
I have an application that makes heavy use of sqlite3 and during load
testing I very, very rarely (read: it has only happened once so far)
occasionally see the following error message:
"BEGIN EXCLUSIVE error: cannot start a transaction within a transaction"
I understand this error messag
On Thu, Sep 28, 2017 at 6:57 AM, Simon Slavin wrote:
> cc: OP
>
> On 27 Sep 2017, at 4:31pm, pisymbol . wrote:
>
> I hope this arrives and gets moderated so someone can look at it.
>
>
> Your mesage and replies to it reached the mailing list without probblems.
> If y
I hope this arrives and gets moderated so someone can look at it.
I am trying to join the sqlite3-users list to ask a technical question but
I never receive a response from the Mailman (and no it isn't in my Spam
folder either).
I apologize if this is not the right address but I don't see an obvi
On Mon, Nov 14, 2016 at 10:51 PM, James K. Lowden
wrote:
> On Mon, 14 Nov 2016 20:30:57 -0500
> "pisymbol ." wrote:
>
> > One last thing: This is during initialization and I access the
> > database through that query several times before hitting this crash.
On Mon, Nov 14, 2016 at 8:26 PM, pisymbol . wrote:
>
>
> On Mon, Nov 14, 2016 at 8:19 PM, Simon Slavin
> wrote:
>
>>
>> On 15 Nov 2016, at 1:18am, pisymbol . wrote:
>>
>> > Obviously, I must be doing something
>> > wrong
>>
>> Yep.
On Mon, Nov 14, 2016 at 8:19 PM, Simon Slavin wrote:
>
> On 15 Nov 2016, at 1:18am, pisymbol . wrote:
>
> > Obviously, I must be doing something
> > wrong
>
> Yep. You're using a 7 year old version of the library.
>
That crash is from me statically li
On Mon, Nov 14, 2016 at 5:13 PM, Stephen Chrzanowski
wrote:
> Can you move project to different hardware?
>
Nope.
Here's at least one stack trace:
#0 sqlite3VdbeUsesBtree (yyp=0x7fffec013a28, yymajor=1, yyminor=...,
pParse=) at sqlite3.c:71844
#1 sqlite3FinishCoding (yyp=0x7fffec013a28, yyma
On Mon, Nov 14, 2016 at 12:38 PM, pisymbol . wrote:
>
>
> On Mon, Nov 14, 2016 at 12:14 PM, pisymbol . wrote:
>
>>
>>
>> On Thu, Nov 10, 2016 at 11:52 AM, Richard Hipp wrote:
>>
>>> On 11/10/16, pisymbol . wrote:
>>> > sqlite-3
On Mon, Nov 14, 2016 at 12:14 PM, pisymbol . wrote:
>
>
> On Thu, Nov 10, 2016 at 11:52 AM, Richard Hipp wrote:
>
>> On 11/10/16, pisymbol . wrote:
>> > sqlite-3.6.20-1.el6_7.2.i686
>> > sqlite-3.6.20-1.el6_7.2.x86_64
>>
>> Are you aware that
On Thu, Nov 10, 2016 at 11:52 AM, Richard Hipp wrote:
> On 11/10/16, pisymbol . wrote:
> > sqlite-3.6.20-1.el6_7.2.i686
> > sqlite-3.6.20-1.el6_7.2.x86_64
>
> Are you aware that SQLite 3.6.20 was published over 7 years ago on
> 2009-11-04 and that there have been 8
Hi:
I'm on Centos 6.8 latest, x86-84.
$ uname -a
Linux (stubbed out) 2.6.32-642.3.1.el6.x86_64 #1 SMP Tue Jul 12 18:30:56
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa sqlite
sqlite-3.6.20-1.el6_7.2.i686
sqlite-3.6.20-1.el6_7.2.x86_64
I have a strange issue that I was hoping familiar with s
17 matches
Mail list logo
