ints, not NOT
NULL constraints.
The UPSERT documentation says "The conflict target specifies a
specific uniqueness constraint that will trigger the upsert." So it
does not explicitly say that UPSERT does not work for NOT NULL
constraints, but that is the implication.
--
D. Richard Hip
e information.
>
> Regards,
>
> Steve
> --
> Stephen Hunt
> Zaber Technologies Inc.
> #2 - 605 West Kent Ave. N.
> Vancouver, British Columbia
> Canada, V6P 6T7
> Toll free (Canada and USA): 1-888-276-8033
> Phone: +1-604-569-3780 ext. 134
;
> Best,
> Manuel
>
>
> [1] 3.28.0 2019-04-16 19:49:53
> 884b4b7e502b4e991677b53971277adfaf0a04a284f8e483e2553d0f83156b50
> [2] 3.29.0 2019-04-27 20:30:19
> 50fe48458942fa7a6bcc76316c6321f95b23dc34f2f8e0a483826483b2fb16f6
>
> On Wed, May 1, 2019 at 9:55 PM Warren Young
d suddenly the order changed because
they left off the "ORDER BY rowid" clause.
So if order is important to your output, *always* use an ORDER BY
clause. Always. No exceptions.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sql
Sorry for the recent spam messages that got through. I accidentally
pressed the "Accept" button rather than the "Discard" button.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailingl
n a result.
I am unable to reproduce the observed behavior. What version of
SQLite are you testing with? Are you compiling it yourself? If so,
what compile-time options do you use?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
ile_format=true;
> VACUUM;
>
> Best,
> Manuel
> _______
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
; sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
forte and I can use all the help I can get!
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 4/29/19, Richard Hipp wrote:
>
> Because assert() can be and is commonly misused, some programming
> language theorists and designers look with disfavor on the whole idea
> of assert(). For example, the Go programming language omits a built-in
> assert(), since the Go developer
ns an invariant(x) statement, I
have much more confidence that the given invariant is true. This
GREATLY enhances maintainability of complex systems, in my experience.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailin
ree with that assessment. Indeed, the
reason why this article exists is to push back against the notion that
assert() is harmful.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sq
et me know if you think the
new paragraph is acceptable or if it needs further revision.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
h I have not actually confirmed that.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
deed a bug, or a misunderstanding on my side?
https://www.sqlite.org/src/tktview/3182d3879020ef3b2e6db56be2470a0266d3c773
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
($file)\n}
}
wapp-subst {\n}
}
wapp-start $argv
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
l, then
that string literal is interpreted as a column name rather than as an
expression. This is done for historical compatibility, and because
there is no point in having an index on a constant expression. See
the implementation at
https://www.sqlite.org/src/artifact/61655dad911a?ln=1319-1341
--
CREATE TABLE 'test'('c0');
Which is logically equivalent to your original:
CREATE TABLE test(c0);
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
variable
> Actual: 404
You do actually have to have the name of the CGI script in there.
Otherwise, althttpd has know way of knowing what script to run.
>
> Test #5:
> Browser URL: http://127.0.0.1:8080/home/index.cgi/some/extra/path/info/
> Expected: same as test 4
> Actual: Uns
p "index.html" around on
websites for legacy links, but new accesses would redirect to "home"
instead.
Which of these URLs do *you* think looks better?
https://wapp.tcl.tk/home/doc/trunk/README.md
https://wapp.tcl.tk/index.html/doc/trunk/README
On 4/26/19, Mohd Radzi Ibrahim wrote:
> Hi, is there a vfs that could be used to open a blob column as a database?
I think you probably want the sqlite3_deserialize() interface.
https://www.sqlite.org/c3ref/deserialize.html
--
D. Richard Hipp
d...@sqlite.
thinks, "I don't
> want to drive that car"?
You will be hard-pressed to buy a new car these days that isn't
running either QNX or Android or both.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailingl
ould keep in mind that I think in terms of the entire
DAG, not individual branches, and so if you are tracking SQLite
development in a Git clone, you should to take steps to ensure that
you do not find yourself stalled on a side-tracked branch.
--
D. Rich
heads
entries are all ephemeral - they are constantly changing on their own,
and no historical record of their past values is retained. So if I
modify the refs to synchronize with the canonical Fossil repository,
how is that changing history, exactly?
Any further explanation is appreciated.
--
D
sting ref it exists
and create a new one if it does not. How might that be done in Git?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ate a new entry refs/heads/mistake
that points to 9b888fcc.
Question 1: Does my analysis seem correct. Or have I misinterpreted
the malfunction?
Question 2: Assuming that my analysis is correct, what is the
preferred way of rewiring the refs in Git?
--
D. Richard Hipp
d...@sqlite.org
_
On 4/20/19, Tony Papadimitriou wrote:
> My SQLite3 repo does not update to the latest. It stopped at 2019-04-17
> [a3ab588329]
>
> c:\sqlite3>fossil up
What happens if you try these commands:
fossil pull
fossil up trunk
--
D. Richard Hipp
ngle character to to LIKE operator, so we had to go back
in and escape that character. The problem is fixed on trunk.
You can find the relevant changes and a reference to the ticket on the
timeline: https://www.sqlite.org/src/timeline?ymd=20190419
--
D. Richard Hipp
d...@sqlite.or
hat there is a slight slowdown here. But for me, this
bisect lands on the same check-in:
https://sqlite.org/src/info/e130319317e76119
This is the bisect:
https://sqlite.org/src/timeline?bid=y736b53f57fn03f2e78899y8eb62fd5fan9cf8ebd141n0888fc2e88y4cdcda408ay6821c61f1dy4678cb10
as separate files in the filesystem.
See https://www.sqlite.org/fasterthanfs.html for further analysis.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
kers choices are quite a much more restricted, and may be an
empty set, depending on the system.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
lities additional security measures. If a value comes from a
bind, then (at least in most systems) that means it did not come from
an SQL injection from an attacker, and hence the value is more
trustworthy.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-u
/thrd5.html#114065
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ly first in release 3.18.0 on 2017-03-28.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ed, and even copy/paste the CLI source
code into your application, if you want.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 4/12/19, Keith Medcalf wrote:
>
> On Friday, 12 April, 2019 12:36, Richard Hipp wrote:
>
>>Perhaps the SELECT is running inside of a transaction that was
>>started
>>before you did the INSERT. For example, perhaps you didn't
>>sqlite3_finalize() the pr
nd
> the INSERT?
Perhaps the SELECT is running inside of a transaction that was started
before you did the INSERT. For example, perhaps you didn't
sqlite3_finalize() the previous SELECT, which caused it to hold the
read transaction open.
--
D. Richard Hipp
d...@sqlite.org
_
e SELECT never sees. This is by design.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
t; to find out what those errors mean.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
the error and warning log
(https://www.sqlite.org/errlog.html)
>
> Regards
> Arun
>
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/l
sqlite.org/checklists/328/index to monitor the
3.28.0 release checklist. we will probably start marking off items
within a day or two. The release will occur when the checklist goes
all green.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing l
affinity(). After inserting a row into table t1:
INSERT INTO t1 values(1,2,3);
You can do:
SELECT affinity(x), affinity(y), affinity(z) FROM v1;
And get the answer:
'text','none','none'
--
D. Richard Hipp
d...@sqlite.org
_
been fixed, and that no new problems have been introduced.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
earching
btrees faster.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
alloca?
>
I think the maximum alloca() allocation will be 7x the page size for
the database file. So a little less than 0.5 MB assuming a maximum
page size of 64K.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailingl
073878dy93386a7c97nd840e9bb02
So it was apparently a bug-fix that caused the performance decrease.
I have not looked into the details yet. Perhaps there is an
alternative fix for the bug that does not cause unnecessary
performance loss.
--
D. Richard Hipp
d...@sqlite.org
On 3/29/19, Joshua Wise wrote:
> Dan, are there any plans to merge the wal2 branch into the trunk?
No, not at this time.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
h
See https://www.sqlite.org/carray.html
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ttps://www.sqlite.org/src/artifact?udc=1&ln=on&name=e7864c391e14ccaf
>>
>> line 481ff, where the "mode" variable is used both to create the file and
>> to create the directory, if necessary.
>>
>> Martin
> ___
> sqlite-users mailing list
>
e of the column, some columns can return different
datatypes (TEXT, BLOB, REAL, INTEGER, NULL) for different rows. To be
fully correct, the library needs to call sqlite3_column_type() for
every column on every row and respond accordingly.
--
D. Richard Hipp
d...@sqlite.org
ty GUI tool.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 3/22/19, R Smith wrote:
> On 2019/03/22 5:30 PM, Richard Hipp wrote:
>>
>> More recent versions of SQLite do issue a warning on the sqlite3_log
>> interface if you use a double-quoted string literal. But not many
>> people look at warnings, it turns out.
>
&g
interface if you use a double-quoted string literal. But not many
people look at warnings, it turns out.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
nal database, before you VACUUM-ed it? If so, what does it
say if you run "PRAGMA integrity_check" on that database.
Can you share the database with me, through private email? There is
always the possibility that the enhanced early detection of corrupt
databases is giving a false-positive.
t;(...)'. In
other words, the sqlite_master.name does not agree with the name in
the CREATE TABLE statement in sqlite_master.sql.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
t them from reverting again.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ou use %q or %Q instead of %s. See
https://www.sqlite.org/printf.html#percentq
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
things. But there is no counter.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
get a segmentation fault.
>
> The query runs error free on PostgreSQL 9.6
>
> The query fails if the 'in' list has more than two entries.
>
> Any ideas?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-
On 3/6/19, Peter Hardman wrote:
>
> I've attached the database file (300K).
>
Attachments are stripped by the mailing list. Please send via private
email directly to me.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing lis
SQLite I have
at hand, and none of them given any trouble. I also ran them under
Valgrind. No problems detected.
Can anybody else reproduce the problem?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqli
t1
>where c=1 and d in (select d from t2 where c=1);
> explain select * from t1
>where c=1 and d in (select d from t2 where t2.c=t1.c);
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
ry that first stumbled over the
heap corruption.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ources.
https://www.sqlite.org/src/info/c7f70b6d96338dba
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 2/28/19, Jean-Baptiste Gardette wrote:
>
> PS : on wich OS did you run the test script ?
> (the different outputs between the two computers gives
> unconfortable feeling)
>
Linux
--
D. Richard Hipp
d...@sqlite.org
___
sqlit
On 2/28/19, Dominique Devienne wrote:
> On Thu, Feb 28, 2019 at 12:14 AM Richard Hipp wrote:
>> Docs have now been updated.
>
> Hi. I don't see it in https://www.sqlite.org/src/timeline.
> Did I miss it? Or is that doc in some other repo?
For historical reasons, the SQLit
meter (maybe $maxReal) and then set
the value using sqlite3_bind_double().
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ou expect in all
three cases, namely 1.79769313486231522322e+308,
8.98846567431157611547e+307, Inf.
SELECT quote(1.7976931348623153E+308);
SELECT quote(1.7976931348623153E+308/2.0);
SELECT quote(1.7976931348623153E+308*2.0);
--
D. Richard Hipp
d...@sqlite.org
ouble. This results in a
> rounding error of the "scale" portion of the calculation (via sqlite3Pow10)
> which results in a false infinity.
>
> Would this be considered a bug, or is precision not guaranteed to the same
> level as strtod because of other factors?
This is a ca
On 2/27/19, lnksz wrote:
> 2) If not, a mention in the docs under disadvantages would be a nice
> information
Docs have now been updated.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.or
imization when there was an ESCAPE
clause and the PRAGMA case_sensitive_like=ON setting was in effect.
That particular combination of circumstances should work, but it did
not. All the other combinations are fine.
The fix is here: https://www.sqlite.org/src/info/6ae4b8c525f446dd
--
D. Richa
unk. The argument can be one of "integer", "real", "text",
"blob", or "any". The "any" is the default and means that SQLite will
use the Tcl_Obj.typePtr to guess at an appropriate type.
--
D. Richard Hipp
d...@sqlite.org
_
On 2/27/19, Stephen Chrzanowski wrote:
> Does write blocking still come into play when using "vaccum into",
The VACUUM INTO command is a reader. So (in WAL mode) some other
process can continue writing while the VACUUM INTO is running.
--
D. Richard Hipp
d.
th TCL and SQLite from
sources. There is no telling what non-standard changes may have been
added by people who assembled your pre-compiled binaries.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
, you should be. Just making
that one change might solve your problem.
In WAL mode, run the entire backup inside a transaction. Or use the
new VACUUM INTO feature to make your backup.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
On 2/27/19, Chris Locke wrote:
> The link you quote mentions SQLite 3.24 though... ?
The problem Niki reported was real. I just have already fixed it.
https://www.sqlite.org/docsrc/info/0a969667a740e806
--
D. Richard Hipp
d...@sqlite.
On 2/27/19, Richard Hipp wrote:
> The modified script can be downloaded from
>
> https://sqlite.orge/tmp/tcl-sqlite-testcase-20190227125331.txt
>
Typo: "sqlite.org", not "sqlite.orge".
https://sqlite.org/tmp/tcl-sqlite-testcase-20190227125331.txt
--
ript, I get:
8.6
8.6.9
{2019-02-26 18:21:08
6d39d6a68bf09e0b4f6706218373e74fc03148fd8bdba5031c3de2f750d87cf2}
# Sequence A
1.00
1.00 text
1.00 text
1.00 text
1.00 blob
1.00 text
# Sequence B
1.00
1.0 real
1.0 real
1.0 real
1.00 blob
1.00 text
# Sequence C
1.00
1.00 text
1.00 text
1.00 text
1.00 b
On 2/25/19, Richard Hipp wrote:
> performance of just over 3GB/sec, which is slightly
> faster than reported simdjson performance of 2.9GB/sec.
Further analysis shows that SQLite was caching its parse tree, which
was distorting the measurement. The following script adds a different
str
script above first measures the length of the input json file
(3327831 bytes) then it parses the file 1000 times. The second second
statement ran in 1.101 seconds (real time) on my 4-year-old linux
workstation, for a performance of just over 3GB/sec, which is slightly
faster than reported simdj
__
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 2/25/19, Robert M. Münch wrote:
> Hi, when doing 2D hit-testing with only rectangular areas, is it faster to
> use the geopoly extension and functions or is the bare R*Tree extension
> faster?
My guess would be bare R*Tree extension, but I have not run the experiment.
--
D. Richa
uld receive an email verification message. Check your spam folder.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
check-ins, but the original content is preserved as part of
the audit trail. The default displays show the corrected information,
but the fact that a correction was applied is easily discerned, and
the original uncorrected content is easily accessible.
--
D. Richard Hipp
d...@sqlite.org
re millions and millions of applications that are coded to the
existing API, so we cannot change APIs.
I rewrote columnName() to completely avoid the use of function
pointers. Perhaps this will appease your compiler.
--
D. Richard Hipp
d...@sqlite.org
__
On 2/19/19, Richard Hipp wrote:
>
> I have checked in a fix on trunk
> (https://www.sqlite.org/src/info/b5f90bfe6295ab3a) but the ticket
> (https://www.sqlite.org/src/info/df46dfb631f75694) has been kept open
> pending further testing and analysis.
Further testing and analysis l
lways great
when we can get a concise and easily reproducible testcase like this.
The fact that you went to the trouble to bisect is above and beyond
the call of duty. Thanks.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users ma
/787fa716be3a7f650cac).
On 2/19/19, Richard Hipp wrote:
> Further debugging hints (for those who are interested):
>
> If you compile with --enable-debug and run the script below, it will
> give you more information about what is going on in the bytecode:
>
> CREATE TABLE IF NOT EX
FROM t1 AS a JOIN t1 AS b ON a.id=b.id WHERE a.id IN (1,2,3);
On 2/19/19, Richard Hipp wrote:
> If you compile with assert() statements enabled (using the
> --enable-debug option with ./configure or otherwise adding the
> -DSQLITE_DEBUG flag) then you will hit an assertion fault earli
INNER JOIN t as b ON a.id = b.id WHERE
> a.id = 1 or a.id = 2 or a.id = 3;
>
> Does /not/ crash.
>
> (and nice work on the bisect! Lol)
>
> -dave
>
>
> ___
> sqlite-users mailing lis
. Or, there might be multiple xBestIndex
calls that all fail for different reasons, in which case it is unclear
which error should be reported.
I will ponder your request. In the meantime, you can continue to use
the old method, which still works like it always has.
--
D. Richard Hi
h trunk page"
>
> "varint are the" -> "varint are"
>
> "not truncate" -> "not truncated"
>
> Best,
> Roland
> _______
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cg
kindly point me to an existing open source implementation.
https://www.sqlite.org/src/file/ext/misc/eval.c
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
of the query
implies that the WHERE clause of the partial index. With your partial
index, you can never prove anything about the truth of the condition
if the query contains "extra>?1". However, if your partial index had
said "WHERE extra IS NOT NULL", then the partial index would be usable
in all of the above situations, since "extra>?1" does indeed imply
that "extra IS NOT NULL".
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
o answer the OP: such an enhancement "seems" simple enough, but
changes to the theorem prover are fraught with peril since if an error
results in a false positive, wrong answers can result. Also, you can
grow a theorem prover without bound, but part of the goal of SQLite is
to remain sma
can define such a function
> and ship it with the binary and it can be used with any database using the
> binary.
Use the sqlite3_auto_extension() interface
(https://www.sqlite.org/c3ref/auto_extension.html) to cause your UDFs
to be registered automatically with all new da
rning any error code.
>
> best regards,
> Radzi
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
ping and rebuilding the index) to try it out, without having to
make any modifications to your application - indeed without having to
recompile your application, or even to restart your application. You
can run experiments with various index configurations to see which one
works best for you.
--
e other rules. In other words, O_DIRECT is not portable - its
operation depends on the specific OS and filesystem you are using.
This seems like an unacceptable solution for a portable library like
SQLite, and so direct I/O is not really a viable solution.
--
D. Richard Hipp
d...@sqlite.org
d the concept? Am I doing something wrong?
New text has been added to https://www.sqlite.org/loadext.html#persist
to hopefully clarify the situation.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http:
301 - 400 of 6449 matches
Mail list logo