Think of floating point as a knapsack problem. The decimal number you want to
represent is the height of the (cylindrical) knapsack. You have a set of
cylinders you want to stack into the knapsack. The IEEE set of cylinders has
the essential property that each cylinder is larger then the sum of
I am facing a crash in sqlite3fts5BufferAppendBlob. Following is the backtrace:
#0 sqlite3Fts5BufferAppendBlob (pRc=pRc@entry=0xf54139c8,
pBuf=pBuf@entry=0xf5afeb90, nData=4294967295, pData=0xf49fff76 "90246ture") at
sqlite3.c:180474#1 0xf717b6f8 in fts5WriteAppendTerm (p=p@entry=0xf54139a8,
Rowan Worth, on Monday, May 27, 2019 11:07 PM, wrote...
>On Mon, 27 May 2019 at 23:36, Jose Isaias Cabrera
>wrote:
>
>> Ok, I think it happens even before the casting. This should be,
>> 3.2598, and yet, it's 3.26.
>>
>> sqlite> SELECT 0.005 + 3.2548;
>> 3.26
>>
On Mon, 27 May 2019 at 23:36, Jose Isaias Cabrera
wrote:
> Ok, I think it happens even before the casting. This should be,
> 3.2598, and yet, it's 3.26.
>
> sqlite> SELECT 0.005 + 3.2548;
> 3.26
>
Note that no arithmetic is required to see these symptoms:
sqlite> SELECT
On 5/26/19, John Brigham wrote:
> I have an Arduino/Python experiment that generates lots of simple
> numerical data; about 7000 records a day. I run it through Python into an
> sqlite3 database.I have been running this for 8 months. I start a new
> database about every six weeks so every data
I have an Arduino/Python experiment that generates lots of simple numerical
data; about 7000 records a day. I run it through Python into an sqlite3
database.I have been running this for 8 months. I start a new database about
every six weeks so every database has about 260k rows. I have one
On 5/27/19 11:36 AM, Jose Isaias Cabrera wrote:
> James K. Lowden, on Sunday, May 26, 2019 04:51 PM, wrote...
>> On Fri, 24 May 2019 13:10:49 +
>> Jose Isaias Cabrera wrote:
>>
Consider these two queries:
SELECT round(3.255,2);
SELECT round(3.2548,2
James K. Lowden, on Sunday, May 26, 2019 04:51 PM, wrote...
>On Fri, 24 May 2019 13:10:49 +
>Jose Isaias Cabrera wrote:
>
>> >Consider these two queries:
>> >
>> > SELECT round(3.255,2);
>> > SELECT round(3.2548,2);
>> >
>> >Do you expect them to give different answer
On 5/27/19 9:16 AM, Simon Slavin wrote:
> On 27 May 2019, at 3:33am, Adrian Ho wrote:
>
>> The OP wants *all users* to be able to update (write) the DB via the Tcl
>> script reading_room.tcl, but *not* by (say) running the SQLite shell or
>> something else. In your setup, as long as a specific u
On 27 May 2019, at 3:33am, Adrian Ho wrote:
> The OP wants *all users* to be able to update (write) the DB via the Tcl
> script reading_room.tcl, but *not* by (say) running the SQLite shell or
> something else. In your setup, as long as a specific user has write
> permissions, *every program*
I experience a memory leak in fossildelta.c using the delta_parse()
table-valued function.
Given this schema:
CREATE TABLE t (x, y, d);
INSERT INTO t VALUES (' +
X'112233445566778899AABBCCDDEEFF',
X'112233445566778899AABBCCDDEE11',
Null);' +
UPDATE t SET d = delta_create(x, y);
This readblob() error message "BLOB write failed" is misleading:
https://www.sqlite.org/src/artifact?ln=79&name=085bbfa57ea58bb1
To me, "BLOB read failed" would make more sense in the readblob() context.
Ralf
___
sqlite-users mailing list
sqlite-use
12 matches
Mail list logo
