SQLITE_LOCKED is an immediate return (that is, it returns immediately, it is
not subject to automatic retries or timeouts or the busy/wait handler -- it is
an error indication, not necessarily a transient condition).
You may use the sqlite3_unlock_notify API (assuming that you have compiled
The trigger program will have update anomalies (violation of the UNIQUE
constraint for example) as well as performance issues unless the data in the
tree is tiny (since it must visit every row in the tree even if it is not being
updated). This will fix those issues (and also requires a
On Sunday, 17 March, 2019 11:19, niklas wrote:
>I agree that correlated subqueries in general seem more natural and
>are probably also less likely to have the performance pessimizations
>noticed with joins.
>But I might also want to use the column, or in case of a correlated
>subquery, the
On Sunday, 17 March, 2019 15:00, Yannick Duchêne
wrote:
>Aside, what also surprised me just a moment ago and I never
>noticed before, is that although I can refer to ROWID (not aliased)
>anywhere in a query, it seems to not work properly in `using(rowid)`, if
>the ROWID is automatically
On Sunday, 17 March, 2019 12:30, Yannick Duchêne
wrote:
>Hi people, it’s a long time I did not get there.
>I’m currently to create and use an SQLite DB with the Python biding
>APSW. For each row returned, I always retrieve the description with
>`Cursor.getdescription()`. Surprisingly, during
nal Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Friday, 15 March, 2019 14:44
>To: SQLite mailing list
>Subject: Re: [sqlite] Query planner: Scanning subqueries vs using
>automatic covering index
>
>
The current tip of trunk produced the same results demonstrated by Niklas in
his original post for his original testcase for me.
I would have written the query as a simple query with correlated subqueries to
get the concatenated data as it is a "more natural" declaration of what is
wanted (in
These docs:
https://sqlite.org/c3ref/expanded_sql.html
The sqlite3_sql and sqlite3_expanded_sql are always be available.
The sqlite3_normalized_sql interface is only available if the
SQLITE_ENABLE_NORMALIZE compile option is used.
---
The fact that there's a Highway to Hell but only a
On Monday, 11 March, 2019 09:42, heribert wrote:
>it works perfect - but i do not understand why.
See https://sqlite.org/lang_with.html for a description of recursive queries ...
>The 'inital-select' results with the head node - only one result set.
>SELECT *
> FROM Tree
> WHERE
elect a, typeof(a), b, typeof(b) from csv2;
a|typeof(a)|b|typeof(b)
1|text|2|text
2|text|3|text
sqlite> select a, typeof(a), b, typeof(b) from test1;
a|typeof(a)|b|typeof(b)
1|text|2|text
2|text|3|text
sqlite> select a, typeof(a), b, typeof(b) from test2;
a|typeof(a)|b|typeof(b)
1|integer|2
I should have said that "It appears that you are correct, the .import shell
command does not know how to create a table in other than the default "main"
schema" and that you are requesting this be changed so that the table being
imported into does get created in the specified schema if a the
On Thursday, 7 March, 2019 14:45, Eric Tsau asked:
>Is it possible to add the option of importing data into a temporary
>table?
>Currently you have to create a temporary table first before importing
>to it, or having to drop the table afterwards.
>.import dump.csv temp.table
>or
>.import
On Wednesday, 6 March, 2019 04:10, Anton Polonskiy
wrote:
>Scenario 1:
>Multiple processes write to foo.db.
>I want to do some periodic snapshots.
>What is the best way to do this without interrupting/blocking
>writers?
>sqlite3 foo.db '.backup snapshot.db' ?
This is the scenario that "vacuum
I was not able to reproduce it. I arrived at the following decoded schema and
query:
CREATE TABLE version (
major_version INTEGER NOT NULL PRIMARY KEY,
minor_version INTEGER NOT NULL,
paradox_upload TEXT,
converted TIMESTAMP NOT NULL,
created TIMESTAMP NOT NULL
);
CREATE
On Tuesday, 5 March, 2019 12:53, James K. Lowden
wrote:
>On Mon, 04 Mar 2019 20:20:08 -0700> "Keith Medcalf"
>wrote:
>> In the first query the subselect that creates the list is
>> independent.
>> In the second query the subselect that creates the list i
On Tuesday, 5 March, 2019 04:09, Simon Slavin wrote:
>On 5 Mar 2019, at 2:06am, kk wrote:
select * from t1
where c=1 and d in (select d from t2 where c=1);
select * from t1
where c=1 and d in (select d from t2 where t2.c=t1.c);
>> DRH, many thanks for your reply, I
On Monday, 4 March, 2019 20:23, Rowan Worth wrote:
>On Sun, 3 Mar 2019 at 20:53, Keith Medcalf wrote:
>> Statements which were in progress that were permitted to proceed
>> (ie, where the next step did not return an abort error) continue
>> with a read lock in place (ie,
In the first query the subselect that creates the list is independent.
In the second query the subselect that creates the list is correlated.
In the first query you have requested that the subquery be executed to create
the list for use by the IN operator. After this has been done the main
to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Saturday, 2 March, 2019 19:52
>To: SQLite mailing list
>Subject: Re: [sqlite]
descriptive).
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Saturday, 2 Mar
>Suppose ROLLBACK does not cancel the BEGIN, can a programmer reliably
>issue more SQL commands, including another ROLLBACK ? Will SQLite
>continue to react correctly to other ROLLBACKs, and to SQL commands
>which result in "(516) SQLITE_ABORT_ROLLBACK".
A successful ROLLBACK on a transaction
BEGIN TRANSACTION
... issued commands inside transaction
COMMIT or ROLLBACK
-- transaction is now closed
That is,
BEGIN "opens" a transaction
COMMIT "closes" the transaction in progress and saves the changes made during
that transaction.
ROLLBACK "closes" the transaction in progress and
On Thursday, 28 February, 2019 21:09, Rishi Mutnuru
wrote:
>I am developing a Multi threaded solution using sqlite3 DB. I know
>there are some issues
>With SQlite3 and python multithreads.
I have never seen a single multithreading problem with Python and SQLite3, at
least not for at least the
Using JOIN ON
is exactly the same as merely listing the tables and pushing the ON into
the where clause. In fact, except for OUTER JOIN operations, the ON clause is
always processed by "pushing" the conditions specified in the ON clause to the
WHERE clause (or you may just think of it as
select a, b, c, g, h, i
from t outer_t, z outer_z
where a == f
and a == 'p001'
and outer_t.idate == (select max(idate) from t where a == outer_t.a)
and outer_z.idate == (select max(idate) from z where f == outer_z.f)
;
This requires that t(a, idate) is unique and that z(f, idate) is
Unable to reproduce:
>sqlite
SQLite version 3.28.0 2019-02-25 18:43:54
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> ATTACH ':memory:' AS 'information_schema';
sqlite> CREATE VIEW
On Monday, 25 February, 2019 05:43, Jonathan Moules
wrote:
>CREATE TABLE error_codes (
> error_code INTEGER PRIMARY KEY
>UNIQUE,
> error TEXT
>);
You do not need (and should not) specify BOTH "PRIMARY KEY" and "UNIQUE". Both
are enforced with a unique
On Friday, 22 February, 2019 09:08, Constantine Yannakopoulos
:
> I would like to find whether an upsert operation actually did an
> insert or an update, preferably without having to execute extra
> SQL statements before or after it.
> I thought of using last_insert_rowid() before and after
On Friday, 22 February, 2019 09:08, Constantine Yannakopoulos
:
> I would like to find whether an upsert operation actually did an
> insert or an update, preferably without having to execute extra
> SQL statements before or after it.
I doubt it very much. You see, an UPSERT statement (or
.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Wednesday, 20 February, 2019 09:44
>To: SQLite Users (sqlite-users@mailinglists.sqlite.org)
>Subject: Re: [sqlite] What is the recommended way
the daftness of some database interfaces.
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: Keith Medcalf [mailto:kmedc...@dessus.com]
>Sent: Wednesday, 20 February, 2019 09:24
>T
Your constraints are logically inconsistent and incompletely specified.
>Alpha has-many Beta,and
>Beta has-many Alpha
>Alpha has-many Charlie, while
>Charlie has one Alpha
Implies that:
Alpha:Beta is N:M and Beta:Alpha is N:M. Fine.
but you did not say whether the instant relationships are
ks I gave
>>help in
>>"reproducing the problem" in a minimal viable way.
>>Don't worry too much about ROWID, there are no deletes/updates on
>our
>>little example.
>>Finally, please reread the OP, I explicitly mentioned the
>>conditions/relations exactl
om: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Keith Medcalf
>Sent: Monday, 18 February, 2019 10:08
>To: SQLite mailing list
>Subject: Re: [sqlite] Reading a table from inside a scalar function
>
>
>SQLite does not maintain state betwee
SQLite does not maintain state between VDBE executions ... each execution is a
context onto itself. Nor is maintain state between separate VDBE executions
executing concurrently. That is to say that the default volatile, SLO_CHNG or
DETERMINISTIC attributes apply only within the execution
The only thing which MIGHT (note that I said MIGHT, you will have to try and
see whether it does or not) make a difference is if you have STAT4 enabled and
have generated statistics on your database. When STAT4 has been enabled AND
you have statistics THEN the query plan is re-prepared after
sqlite3_exec still prepares an SQL query and executes it with step. It is
merely syntactic sugar (a convenience wrapper) around the standard prepare and
step procedure.
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
You do it the same way you do in any C function. You obtain a handle to the db
connection (which is very conveniently passed to your UDF), you prepare and
execute the sql statement, retrieve the results of that execution, compute your
response, and return it from the UDF function.
---
The
l?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>On Mon, Feb 18, 2019, 10:56 AM Keith Medcalf wrote:
>
>>
>>
>> create table coaches (coach_name text);
>>
>> create table players (
>&g
>
>Thanks. I am new to SQL and DB in general; please clarify what *is it
>valid* means. How do I check validity of schema?
>
>On Mon, Feb 18, 2019, 1:17 AM Keith Medcalf wrote:
>
>>
>> Nice schema. Do you have a valid one?
>>
>>
>> ---
>>
Nice schema. Do you have a valid one?
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Rocky Ji
>Sent:
See also SQLITE_EXTRA_INIT
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Arun - Siara Logics
>(cc)
You should probably read the documentation.
https://sqlite.org/lang_altertable.html
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
insert into t (a, b, c, d, e, idate)
values ('p001', 1, 2,
(SELECT d FROM t
WHERE a = 'p001'
ORDER BY idate desc
limit 1
),
4, '2019-02-12');
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original
Must be whatever the ICU collating sequence does. It apparently sorts into an
order you like, but does not sort the characters as being "the same". Unless
they are "the same" they will not be in the same group.
The unifuzz "unaccented" collation does sort the two characters as "the same"
On Thursday, 7 February, 2019 22:47, li...@herger.net wrote:
>> COLLATE affects SORTING, it does not transmorgify the "value" of
>the thing to which it is applied. That is, name COLLATE means
>that the item name is SORTED using the collating sequence , not
>that the result of "name
COLLATE affects SORTING, it does not transmorgify the "value" of the thing to
which it is applied. That is, name COLLATE means that the item name is
SORTED using the collating sequence , not that the result of "name COLLATE
" is transmorgified into tha value that is used for
You mean something like
select *
from t
where a in (select a from t where e != 1
union
select a from t where d > 3
union
SELECT a from t where c != 1 AND b != 1);
or more succinctly:
select *
from t
where a in (select a
sqlite3 database.db < myscript.sql
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of kostasvgt
>Sent:
On Wednesday, 6 February, 2019 12:55, Ben Asher wrote:
> Hi there! We're having a debate at my company about date storage in
> SQLite. SQLite has builtin support for ISO8601 in its date functions,
> so some folks have started storing dates as ISO8601 SQLite-compatible
> date strings.
> Are
On Tuesday, 5 February, 2019 15:12, Gerlando Falauto wrote:
> I could've just used directories and logfiles instead of abusing
> a relational database but I just thought it would more convenient
> to issue a query and use a cursor.
Well, the "abusing a relational database" is the correct
Fascinating. From the same source table see also:
sqlite> select tab2.id is not null as c from tab left join tab as tab2 on 0
where c = 0;
QUERY PLAN
|--SCAN TABLE tab AS tab2 (~983040 rows)
`--SCAN TABLE tab (~1048576 rows)
sqlite> select tab2.id is not null as c from tab left join tab as
>I wonder if I'd be allowed to add an ORDER BY in the subquery and if
>that would make any difference -- I remember reading ORDER BY is only
>allowed in the outer query (which makes perfect sense).
Yes, you can use an order by in a subquery (either a correlated subquery or a
table generating
e the b-tree is *NOT* for "RIGHT PART OF" ORDER BY, it seems like
>some
>global sorting
>which looks even worse than case 2.
>
>What am I doing wrong? Is this expected?
>I just don't seem to be able to get what would have been a pretty
>trivial
>task with
>last-centur
Using the transitive_closure virtual table extension (closure.c) on your
original question (my sqlite3 has everything built-in already, so no need to
load the extension):
Note though that the AVL tree generated by the closure extension is generated
on the fly upon request and does not have a
On Tuesday, 29 January, 2019 16:28, Wout Mertens wrote:
>To: SQLite mailing list
>Subject: Re: [sqlite] SQLite slow when lots of tables
>
> I always have to explain to people that there's no magic sauce that
> "real databases" add versus SQLite.
> SQLite uses the same techniques all databases
See https://sqlite.org/lang_with.html
which includes how to traverse the recursive tree in either depth-first or
breadth-first order.
Why do you need the closure table at all?
create table folders
(
idinteger primary key,
parent_id integer references folders,
name
Do you perhaps want this:
select source1,
source2,
(
select min(ts)
from rolling
where source1 = x.source1
and source2 = x.source2
)
from (
select distinct source1,
source2
from rolling
Your description of the schema does not match the schema that you have shown.
(As an aside, I wonder why you are using such confusing table and column names
that require the puking of quotes all over the place? You can avoid such
ugliness by searching and replacing all "-" with nothingness
There are a few reasons for putting code in a DYNAMIC link library (linked at
runtime) versus statically linked into the application (the same applies to all
operating systems that support runtime linkage no matter what they call the
runtime linked modules):
1) You need to be able to replace
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 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
>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
The reason for this is historical and is because Microsoft SQL Server is a
derivative work of Sybase SQL Server and their TRANSACT-SQL language. Sybase
was the first (I believe) SQL-based RDBMS that supported a complete and ONLY
dynamic execution model for SQL statements. All other DBMS
SQLite3 does have variables.
You set them by binding values to an SQL statement, and retrieve them by
retrieving column values resulting from the execution of an SQL Statement. For
example:
sqlite3_prepare('select var1, var2 from table1 where val3=?;')
You bind a value to the val3
Are you getting as OS ERROR 5 or the SQLITE Return Code 5 (SQLITE_BUSY).
The former means that the OS is indicating that the USERID you are using to run
the task cannot open the file or the directory or the temporary files or the
journal files required because it has not been granted the
>For the OPTIMIZE the documentation states: "... run just before
>closing each database connection ...". There isn't a reason to do it
>instead after opening a connection each time?
The documentation tells you under what circumstances PRAGMA OPTIMIZE does
anything, in the current implementation.
On Friday, 4 January, 2019 04:31, Cecil Westerhof wrote:
>I have the following query:
>SELECT MIN(totalUsed) - 1
>FROM quotes
>WHERE totalUsed <> 'notUsed'
>What I want is that when the SELECT returns a positive value every
>record where totalUsed <> 'notUsed' is lowered with the returned
On Thursday, 3 January, 2019 03:33, Dominique Devienne
wrote:
>PS: Strange how the compiler is reported as GCC 5.2. Mingw-build?
>Instead of native MSVC? Cross-Compiled?
>C:\Users\ddevienne>sqlite3 -version
>3.26.0 2018-12-01 12:34:55
On Wednesday, 2 January, 2019 16:58, Jonathan Moules
wrote:
>Gah, sorry. Another typo. I really should be more awake when I post
>to this list. The non-simplified code does have the item_id on the
>subquery (otherwise it simply wouldn't execute at all of course). So:
>SELECT *
> FROM
When you are executing the query:
SELECT *
FROM item_info
JOIN (select count(1)
from users
group by item_id)
USING (item_id)
where item_id = ?;
You are telling the SQL Database Engine (whatever it may happen to be, in this
case SQLite3) that you want to take the table
However, if you want to do that then you want to use a correlated subquery as
it is designed for retrieving correlated data by running a subquery per result
row:
select *,
(select count(*) from users where item_id = item_info.item_id) as count
from item_info
where item_id = ?;
and
ists.sqlite.org
>Subject: Re: [sqlite] Using sqlite3_interrupt with a timeout
>
>On Mon, 31 Dec 2018 14:25:41 -0700
>"Keith Medcalf" wrote:
>
>> def run_query_with_timeout(db, query, timeout, whizround)
>> stmt = prepare(db, query)
>> create_thread A
SQLite 3.27.0 2018-12-31 21:43:55
b57c545a384ab5d62becf3164945b32b1e108b2fb4c8dbd939a1706c2079alt2
zlib version 1.2.11
gcc-8.1.0
sqlite> select degrees( radians(175) + atan2( sin(radians(90)) *
...> sin(0.2/6378.14)*cos(radians(-42)), cos(0.2/6378.14) -
...>
UNABLE TO REPRODUCE.
Your CREATE TABLEs do not work (they contain syntax errors).
The query you complain about taking a long time does not and cannot work
because it is attempting to join two tables using a common column name, that
column name NOT being contained in one of the tables
On Wednesday, 2 January, 2019 03:06, Dominique Devienne
wrote:
>On Mon, Dec 31, 2018 at 10:31 PM Keith Medcalf wrote:
>>> I don't think the interrupt call will actually terminate a step
>>> that is actually being processed, but only mark that no more steps
>>>
>I don't think the interrupt call will actually terminate a step that
>is actually being processed, but only mark that no more steps should
>happen. In other words, I don't think SQLite is spending time
>checking a flag to stop in the middle of processing a step to allow the
>processing to
That is, of course (I forgot the stmt argument to sqlite3_stmt_busy in all the
whizing around):
def interrupt_function(db, stmt, timeout, whizround)
while whizround and !sqlite3_stmt_busy(stmt) /* whizround waiting for
statement to start */
sleep(0.001)
On Monday, 31 December, 2018 13:48, Simon Slavin wrote:
>On 31 Dec 2018, at 8:18pm, Jesse Rittner wrote:
>> I'm trying to write a function to run a query with a timeout. If
>> the timeout expires, the query must stop execution within a "reasonable"
>> amount
>> of time.
>There is no rule
On Monday, 31 December, 2018 13:19, Jesse Rittner
wrote:
>Keith Medcalf wrote
>> What are you trying to accomplish? Perhaps what you really want is
>> a progress callback?
> I'm trying to write a function to run a query with a timeout. If the
> timeout expires, the quer
>To be clear, is it sqlite3_step returning SQLITE_DONE that marks it
>as "not running", or calling sqlite3_reset/sqlite3_finalize?
Well, "running" means that execution has commenced (the first call to
sqlite3_step has been made on the statement) and the execution has not yet
completed.
"RUNNING" means that the statement is running. When you call sqlite3_prepare,
SQLite3 generates a PROGRAM which will "yield" the results of the execution of
that SQL statement. It looks something like this:
START:
... do stuff ...
LOOP:
... do stuff ...
return a result row (SQLITE_ROW)
>Another interesting distinction between shared and private cache mode
>I found while experimenting. Ordinarily if connection A is in the
>middle of fetching result rows from a SELECT (i.e., sqlite3_step was called,
>but not sqlite3_reset), and connection B tries to do a CREATE/UPDATE/DELETE,
>B
The "normal" connection mode would be to have a separate connection for each
thread, with no shared cache. Each connection is opened with the FULLMUTEX
(serialized) flags. This is the default. Each connection is fully isolated
from every other connection. Assuming that each "thread" has
You can always turn your 100/count(ID) into a scalar expression (so that it is
only calculated once):
select ID,
(count(Quantity) over Win1) * (select 100.0/count(ID) from mytable) as
Percentile
from myTable
Window Win1 as (order by Quantity range between unbounded preceding and current
row);
Quite the difference indeed ...
sqlite> .once q2
sqlite> WITH RECURSIVE tree(child_id, parent_id, steps) AS (
...>SELECT child.id AS child_id, child.id AS parent_id, 0 AS steps
...>FROM languoid AS child
...>UNION ALL
...>SELECT tree.child_id AS child_id,
gt;and dll files in my project directory? Sorry for my denseness. I'm
>very knew to this route of doing things, old as that route may be.
>
>
> From: Keith Medcalf
> To: SQLite mailing list
> Sent: Friday, December 21, 2018 5:15 PM
> Subject: Re: [sqlite] Need setu
>that I was able to talk through to something. I'll try your code
>below.
>
>Thanks MUCHO.
>
>David
>
> From: Keith Medcalf
> To: SQLite mailing list
> Sent: Friday, December 21, 2018 4:53 PM
> Subject: Re: [sqlite] Need setup code for VC++ 2017 that
First of all use EITHER the source (.c) OR the precomiled dynamic link library
(.dll/.lib). Not both.
The .c file contains the code to the sqlite3 database engine. The DLL contains
this code compiled to a Dynamic Link Library. The LIB file tells your
application how to find the code in
C++ is just C with mungified names and structures with pointers. You can call
C functions from C++. You compile the "C" stuff as "C" and the "C++" stuff as
"C++". You then link them together to produce as executable.
In order to generate a "load module" output (ya know, that EXE thing that
Only if the application were so badly written as to permit the execution of
untrusted code ...
---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a
lot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
On Thursday, 20 December, 2018 17:32, Jens Alfke wrote:
>> On Dec 20, 2018, at 4:21 PM, Jungle Boogie wrote:
>> select od_reading from mileage where car='foo' limit 1
>> select od_reading from mileage where car='bar' order by od_reading
>> desc limit 1
>Note: the first query should use
>All I meant was that with a decimal exponent, the units could be
>dollars,
>and additions and subtractions of cents would be exact (assuming the
>mantissa has enough bits), with no worries about rounding. Which is
>the
>basis for this whole discussion.
This is called fixed point. All that is
On Tuesday, 18 December, 2018 14:50, Nathan Green wrote:
>Except the problem isn't just in Chrome. Apparently, any system that
>allows SQL injection is vulnerable. Since SQLite can be used as a file
>format to transport application data
>(https://www.sqlite.org/appfileformat.html),
>other
Why shocked?
Chrome allows direct execution of untrusted and likely malicious code that it
gets over the network. It is called JavaScript. That a new method for
execution of untrusted remote malicious code has been created is completely
unsurprising since the whole point of Chrome is to
>This thread is getting out of hand. Firstly there is no such binary
>representation ( in this universe ) for a trivial decimal number such
>as one tenth ( 0.10 ) and really folks should refer to the text book
>recently published ( 2nd Edition actually ) where all this is covered
>:
> Handbook
On Monday, 17 December, 2018 12:27, Jay Kreibich wrote:
>> On Dec 17, 2018, at 1:12 PM, Keith Medcalf wrote:
>> The "nearest" representation of 211496.26 is
>> 211496.260931323. The two representable IEEE-754 double
>> precision floatin
The "nearest" representation of 211496.26 is 211496.260931323. The two
representable IEEE-754 double precision floating point numbers bounding
211496.26 are:
211496.260931323
211496.25802094
The difference between 211496.252 (which is itself a truncated
ginal Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Wout Mertens
>Sent: Sunday, 16 December, 2018 07:55
>To: SQLite mailing list
>Subject: Re: [sqlite] Question about floating point
>
>On Sat, Dec 15, 2018 at 7:13 PM Keith Medcalf
On Saturday, 15 December, 2018 10:54, Simon Slavin wrote:
>On 15 Dec 2018, at 5:35pm, Keith Medcalf wrote:
>> Fast forward 25 years and you would these days be hard pressed to
>find a computer that DOES NOT use proper IEEE-754 floating point and
>that DOES NOT default to a mi
501 - 600 of 1993 matches
Mail list logo