Okay, I put in some instrumentation. Basically I print out all database
queries as they happen, along with all calls to sqlite3OsLock() and
sqlite3OsUnlock() (including their lockType argument and any abnormal return
code). Also I print out how many times sqlite3InvokeBusyHandler() has to
There does exist an experimental branch which introduces the concept
of shell variables.
https://www.sqlite.org/src/timeline?r=shell-bindings
The check-in comment describes the usage:
"Add the ability to use bind parameters in the CLI. The new ".set
KEY=VALUE" dot-command works to set bindings.
Keith Medcalf wrote:
> Andy Goth wrote:
>> There are two possibilities:
>>
>> 1. Transactions do work, but I'm misusing them and must learn how to be
>> more careful. In this case, I will update documentation to properly
>> explain their use to others.
>>
>> 2. Transactions don't work, at least
On Sunday, 20 January, 2019 17:19, Simon Slavin wrote:
>> If the issue is the dead lock, you get similar issues with all
>> DBMSes.
> I'm not perfectly sure of my logic here, but OP posted elsewhere that
> replacing BEGIN with BEGIN IMMEDIATE cures the problem. I think this
> indicates that
On 20 Jan 2019, at 11:54pm, Richard Damon wrote:
> If the issue is the dead lock, you get similar issues with all DBMSes.
I'm not perfectly sure of my logic here, but OP posted elsewhere that replacing
BEGIN with BEGIN IMMEDIATE cures the problem. I think this indicates that his
problem
On Sunday, 20 January, 2019 16:32, Thomas Kurz wrote:
>Just for curiosity: how do other DBMS (MySQL, etc.) solve this issue?
>I guess the keypoint is that no matter where the query comes from,
>the database files are always under control of the same process which
>then can take care of the
On 1/20/19 6:32 PM, Thomas Kurz wrote:
> Just for curiosity: how do other DBMS (MySQL, etc.) solve this issue? I guess
> the keypoint is that no matter where the query comes from, the database files
> are always under control of the same process which then can take care of the
> correct order
Just for curiosity: how do other DBMS (MySQL, etc.) solve this issue? I guess
the keypoint is that no matter where the query comes from, the database files
are always under control of the same process which then can take care of the
correct order in which to read and write data.
But the
On 1/20/19 4:51 PM, andrew.g...@l3t.com wrote:
> James K. Lowden wrote:
>> On Sat, 19 Jan 2019 08:07:42 -0500 Richard Hipp wrote:
>>> The busy timeout is not working because you start out your transaction
>>> using a read operation - the first SELECT statement - which gets a read
>>> lock. Later
>There are two possibilities:
>1. Transactions do work, but I'm misusing them and must learn how to
>be more careful. In this case, I will update documentation to
>properly explain their use to others.
>2. Transactions don't work, at least not for my task. In this case,
>I will do my best to
James K. Lowden wrote:
> On Sat, 19 Jan 2019 08:07:42 -0500 Richard Hipp wrote:
>> The busy timeout is not working because you start out your transaction
>> using a read operation - the first SELECT statement - which gets a read
>> lock. Later when you go to COMMIT, this has to elevate to a
Darn ti! Thanks.
On Saturday, January 19, 2019 07:20 AM, J. King wrote,
>On January 18, 2019 12:54:32 PM EST, Jose Isaias Cabrera
>wrote:
>>
>>sqlite> select a.a, a.b, a.c, b.d, b.e as q from a join b on a.a=b.a
>>where a.a = 1;
>>sqlite>
>>
>>This provides no result. I expected to get,
>>
On Sat, 19 Jan 2019 12:01:34 -0700
"Keith Medcalf" wrote:
> Microsoft took the OS/2 3.0 Beta 2 code and generated their OS/2 New
> Technology. The "New Technology" part was considered to be a bit to
> long, so Microsoft shortened it to NT, replaced the Presentation
> Manager with with Windows
On Sat, 19 Jan 2019 08:07:42 -0500
Richard Hipp wrote:
> The busy timeout is not working because you start out your transaction
> using a read operation - the first SELECT statement - which gets a
> read lock. Later when you go to COMMIT, this has to elevate to a
> write lock. But SQLite sees
Hello Scoott !
I have done some work with a prototyping tool for data applications
using sqlite https://github.com/mingodad/db-api-server and use for
navigate several opendata sources like (sorry it is in Spainsh)
https://meimporta.eu look here
https://borme.w.meimporta.eu/bormeMalaga-lm.app
Which problem did you experience on SPARC?
It is a nearly impossible process. Can not be done unless you have a
very specific class of hardware.
Really? SQLite3 builds quite happily on the various SPARC S8 ...
Can we stop talking about historical hardware? I have Apache httpd
running
You can try reading the Fossil source code to see how it handles full-text
searching across multiple tables.
https://fossil-scm.org/index.html/artifact?fn=src/search.c=trunk
On Sat, Jan 19, 2019, 06:10 Scott
> I apologize, I sent this from a different email than I registered
> accidentally.
>
On 20/01/2019 15:03, Dennis Clarke wrote:
On 1/19/19 10:55 AM, Igor Korot wrote:
Dennis,
On Sat, Jan 19, 2019 at 9:31 PM Dennis Clarke
wrote:
And SPARC version is still available for download...
Let us know when you get that running.
Install of x86 went very smooth.
The x86_64
On 1/20/19 12:50 AM, Gary R. Schmidt wrote:
On 20/01/2019 15:03, Dennis Clarke wrote:
On 1/19/19 10:55 AM, Igor Korot wrote:
Dennis,
On Sat, Jan 19, 2019 at 9:31 PM Dennis Clarke
wrote:
And SPARC version is still available for download...
Let us know when you get that running.
19 matches
Mail list logo
