put needs to be dealt
> with as text.
> Is there any SQLite API that can help me with this?
>
> sqlite3_column_type and sqlite3_column_decltype can't tell me this
> information.
sqlite3_column_type() should be returning SQLITE_TEXT, unless there is
something wrong with your UDF.
es,
> etc.
>
correct
--
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
);
CREATE INDEX t1b ON t1(b);
CREATE INDEX t1c ON t1(c);
SELECT a FROM t1 WHERE b=5 AND c=9;
PRAGMA optimize(-1);
Looks like the argument to optimize should be -1, not 1, in order to
see the debugging output.
--
D. Richard Hipp
d...@sqlite.org
___
sqlit
PRAGMA optimize(1)".
--
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
hen run some query that could
potentially use either index. Then when you run "PRAGMA optimize" it
will tell you that you should run ANALYZE on that table.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@
arried forward to preserve 100% API compatibility.
>
> Will I miss anything if I cast out "unsigned"?
No.
--
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
lite.org//sqlite3-dll-win32-x86-.zip or
https://sqlite.org//sqlite3-dll-win64-x64-.zip where
is 2013, 2014, 2015, 2016, or 2017.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists
efunc.html
To get the date-and-time for "9am the next day" given a numeric
timestamp as a julian day number:
SELECT datetime(numericJDTime, 'start of day', '+33 hours');
If you timestamp is unix (seconds since 1970):
SELECT datetime(numericUnixTime, 'unixepoch', 'start of d
d to have a recent "tclsh" installed on your machine in
order to run step 3.
--
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
a bug in the new sqlite3_result_pointer()
interface. I added a proposed patch to the ticket. But we are still
working on getting a test case here.
The problem, if my analysis is correct, should be obscure and require
a very specific query to hit.
--
D. Richard Hipp
d...@sqlite.org
__
t;
> HTH
>
> Dennis Cote
>
> ___
> 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
_
:
https://sqlite.org/src/timeline?c=d0da791ba0edfb65=ci
--
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 8/18/17, Gerry Snyder <mesmerizer...@gmail.com> wrote:
> Should it be :
>
> CREATE UNIQUE INDEX ...
I don't think it matters in this case. The trigger is also enforcing
uniqueness.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-use
force uniqueness on k for INSERT statements. You'll
want a second "BEFORE UPDATE" trigger to do similar enforcement for
UPDATEs if that is an issue for you.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-use
On 8/16/17, Simon Slavin <slav...@bigfraud.org> wrote:
>
> I worked at a university and we used network home directories.
Why use the local disk when you can instead use a network filesystem
that is less reliable and about 100x slower?
--
D. Richard Hipp
d..
On 8/16/17, Jens Alfke <j...@mooseyard.com> wrote:
> So may I request taking out this #warn directive?
>
You can probably make the warning go away if you compile with
-DSQLITE_ENABLE_LOCKING_STYLE=0
--
D. Richard Hipp
d...@sqlite.org
___
arison.
Remember: COLLATE binds more tightly than ==. So
'xyz' = 'XYZ' COLLATE nocase
gets parsed out as
'xyz' = ('XYZ' COLLATE nocase)
And that expression has a different meaning from your
('xyz' = 'XYZ') COLLATE nocase
--
D. Richard Hipp
d...@sqlite.org
_
ike to have their home
directories NSF-mounted.
--
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
" should look like the tables "test2" and
> "test4".
>
> Regards,
> Jürgen
> ___
> 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
an use the DBSTAT virtual
table (https://www.sqlite.org/dbstat.html) to query for that
information on a page-by-page basis.
For indexes and WITHOUT ROWID tables, the keys can be much larger, and
so the minimum-four-per-page rule is more likely to come into play.
--
D. Ric
to avoid confusion. The actual work of seeking
on the main table cursor is deferred until there is a read request on
that cursor. And no read request every occurs, and so the seek never
happens.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
rate.
I think fixing that should be low-priority.
--
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 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 8/10/17, Drago, William @ CSG - NARDA-MITEQ <william.dr...@l3t.com> wrote:
> The word hold should be holds in the first sentence of section 3. The
> Rollback Journal. In the 3rd sentence give should be given:
>
Fixed now. Thanks.
--
D. Richard Hipp
On 8/10/17, Jens Alfke <j...@mooseyard.com> wrote:
>
> If I were going to use it, I’d implement a pair of SQL functions to
> compress/uncompress blobs,
See https://www.sqlite.org/src/file/ext/misc/compress.c
--
D. Richard Hipp
arch" option on the far right of the menu bar. Click it. In the
search box type in "books" and then press "Go". Following the first
hyperlink in the search results.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailin
it
> provide only a basic key/value store API?
It is just a separate key/value store using a different file.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi
A fix is now on trunk. https://www.sqlite.org/src/info/795eede331b832a5
On 8/8/17, Richard Hipp <d...@sqlite.org> wrote:
> On 8/8/17, Gavin Rayner <rayner.ga...@gmail.com> wrote:
>> Hi,
>>
>> I’m new to sqlite and C. I get this error whilst trying to compile
appreciated.
>
> Regards,
>
>
> Gavin Rayner
>
>
> _______
> 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 8/8/17, x <tam118...@hotmail.com> wrote:
> I keep reading about this LSM1 but can’t find anything about it beyond
> tickets. Any links?
Baseline technology: https://en.wikipedia.org/wiki/Log-structured_merge-tree
No documentation yet on the LSM1 implementation in SQLite.
--
D.
tf-8');
PRAGMA encoding('utf-16be');
PRAGMA encoding('utf-16le');
See https://www.sqlite.org/pragma.html#pragma_encoding for additional
information.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglis
t; Unicode-encoded by Unicode-aware software and OS, with no mistakes about how
> Unicode should be done.
>
> Can I persuade the SQLite shell tool to spit out the characters string in
> Hex ? Perhaps by casting it to a BLOB ?
Use the hex() SQL function.
--
D
n getting it there, and also the amount of other
distractions that would draw our attention away prior to the 3.20.0
release.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bi
On 8/5/17, Bart Smissaert <bart.smissa...@gmail.com> wrote:
>
> SQLite_stmt doesn't hold the statement handle...
> I wonder why this is.
>
Because that would be a "pointer leak". https://sqlite.org/bindptr.html#ptrleak
--
D.
On 8/4/17, Charles Leifer <colei...@gmail.com> wrote:
>
> My excitement quickly turned to disappointment as I realized that the
> extension is unusable for all practical purposes:
>
Yes, it needs work. That is why it is unannounced.
--
D. Richard Hi
text, by visiting
"sqlite3.org/src/timeline?c=$HASM". For example:
https://sqlite.org/src/timeline?c=9501e22d
--
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
server-process-edition branch
(https://sqlite.org/src/timeline?n=all=server-process-edition) which
you can read about here:
https://sqlite.org/src/artifact/0c6bc6f55191b690
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqli
thing. The ".timeout" command (which I had
forgotten about) existed long before the "PRAGMA busy_timeout" command
was created. Both commands invoke sqlite3_busy_timeout() for you.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-use
an you please provide more details on how having a dynamic string for
the pointer type would be helpful? What is it that you are trying to
do that string constant will not work? Please be as specific as
possible, so that I might better understand your problem.
--
D. Richard
e case. It
> might be a hurdle for unsophisticated developers, but not for the
> experienced ones.
>
The documentation has now been adjusted to try to make it clear that
the static string requirement simply makes misuse of the interface
more difficult, not impossible.
--
D. R
On 8/3/17, J. King <jk...@jkingweb.ca> wrote:
> The fifth paragraph of
> <https://sqlite.org/bindptr.html#destructor_functions> ends after two
> words, "Note that".
>
Thank you. Should be fixed now.
--
D. Richard Hipp
d...@sqlite.org
__
. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
ps://twitter.com/ThinkSmartbox> LinkedIn
> <https://www.linkedin.com/company/smartbox-assistive-technology> YouTube
> <https://www.youtube.com/user/SmartboxAT>
>
> Smartbox Assistive Technology, Ysobel House, Enigma Commercial Centre,
> Sandys
> Road, Malvern, WR1
that multiple threads cannot be making updates at
the same time. In this case, the update would be happening in the
same thread.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.
On 7/31/17, Jeffrey Mattox <j...@mac.com> wrote:
> Is there any way to predict what error a (buggy) legacy app will receive, or
> is that dependent on the wrapper?
Dependent on the wrapper, unfortunately.
--
D. Richard Hipp
d...@sqlite.org
__
operate as before with no changes.
Nevertheless, I encourage you to download a copy of the latest release
candidate and try it for yourself, to see if you have any problems.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@maili
On 7/31/17, jose isaias cabrera <jic...@barrioinvi.net> wrote:
>
> Funny. :-) (the sneezing lately...)
>
> I say, let's add the change to 3.20.0.
The patch is on the 3.20.0 branch. We are testing the 4th release
candidate now.
Thanks for the feedback.
--
D. Richard Hi
to me is also accepted.
--
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
nd_pointer() and
sqlite3_result_pointer() interfaces.
This change will delay the 3.20.0 release by several days.
Please report any issues or concerns on this mailing list, or directly
to me. Thanks.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sq
_pointer(),
sqlite3_result_pointer(), and sqlite3_value_pointer() design? Are
there multiple complains? Can you enumerate them? Please be as
specific as possible.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.
cles
for the overwhelmingly common case where pointers are not being
passed. We do not want to burden the common case for the convenience
of an outlier.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@m
atabase file is on
disk, the statement log is a temporary file on disk which you are not
noticing. But when the database file is ":memory:" the statement log
is also in memory. 500K transactions at 4KB per page accounts for
most of the 2GB
On 7/25/17, David Wellman <dwell...@ward-analytics.com> wrote:
> Hi,
>
> Minor doc error at https://sqlite.org/draft/bindptr.html
>
Typo fixed. Thanks.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing
date is one week from today. If you have concerns
with anything in this release, please raise them now.
The checklist at https://sqlite.org/checklists/320/index has been
reset. The release will occur when that checklist goes all-green.
--
D. Richard Hipp
d...@sqlite.org
ically to identify validated JSON text in
the JSON1 extension) and will continue to live on to serve those
unrelated purposes.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.o
https://www.sqlite.org/draft/bindptr.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
On 7/21/17, petern <peter.nichvolo...@gmail.com> wrote:
>
> How was adding to the BLOB API ruled out?
It uses extra memory and CPU cycles, even on the vast majority of
applications that do not use it.
--
D. Richard Hipp
d...@sqlite.org
__
On 7/21/17, Peter Da Silva <peter.dasi...@flightaware.com> wrote:
> I assume BEGIN, COMMIT, and ROLLBACK are safe too :)
Yes, of course.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite
base in any that make it unreadable by X.
"DML statements" = SELECT, INSERT, UPDATE, DELETE.
--
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
e C++ templates or other
interfaces that work with arbitrary types. Each use of _pointer() is
intended to be used for a single narrowly defined purpose.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite
eek
or two.
--
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
/17/17, Keith Medcalf <kmedc...@dessus.com> wrote:
>
> On Monday, 17 July, 2017 08:00, Richard Hipp <d...@sqlite.org> wrote:
>> On 7/17/17, Keith Medcalf <kmedc...@dessus.com> wrote:
>
>> > Also, a question. sqlite3_bind_pointer(C, P, T) and
>> &
he failure case in question was in
3.20.0 in response to your original bug report.
--
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
laiming "Wow! What a Ride!"
> -- Hunter S. Thompson
>
>
>
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlit
c:
>
> "The pointer type is a string that must compare equal using strcmp() or
> else the pointer comes through as a NULL."
>
> On Thu, Jul 13, 2017 at 11:49 AM, Richard Hipp <d...@sqlite.org> wrote:
>
>> The 3.20.0 release of SQLite is expected in about a w
.
Curiously, there was an assert() that should have failed in the code
generator for this problem. But I coded the assert() incorrectly.
:-)
Both the original problem and the assert() will be corrected when the
fix is checked in.
--
D. Richard Hipp
d..
his time - something that we
should fix for the next release.)
I still power up a PPC mac from time to time in order to verify that
SQLite works on big-endian platforms. But it is painfully slow. Why
are you still using a PPC mac?
--
D. Richard Hipp
d...@sqlite.org
The STMT extension has been renamed as SQLITE_STMT.
Updated code is in the prerelease snapshot on
https://sqlite.org/download.html and the draft documentation
(https://sqlite.org/draft/index.html) has been updated.
--
D. Richard Hipp
d...@sqlite.org
t;
> Thank you in advance!
>
>
>
>
>
>
>
> --
> View this message in context:
> http://sqlite.1065341.n5.nabble.com/Porting-SQLite-Stack-error-tp96609.html
> Sent from the SQLite mailing list archive at Nabble.com.
> _______
te code, we figured
it would be good to publish it to perhaps help others notice subtle
problems in their code.
--
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
erface that will not change) is that
SQLITE_PREPARE_PERSISTENT is a hint to SQLite that the prepared
statement is going to linger for a long time.
How would you recommend that be stated more clearly?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@m
easelog/3_0_0.html) so I think I will leave
it. All other fixes implemented.
--
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
or general consumption, yet.
--
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
_20_0.html
You can send issues to this email list, or directly to me.
--
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
nerated code, but not nearly as bad as ICC. I have not
studied the machine code generated by clang to see what the difference
is, as I just did for ICC.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sql
On 7/9/17, Bob Friesenhahn <bfrie...@simple.dallas.tx.us> wrote:
> On Sat, 8 Jul 2017, Richard Hipp wrote:
>>
>> gcc-5.4: 491585 bytes, 1,124 million CPU cycles.
>> icc-17.0: 536596 bytes, 1,274 million CPU cycles
>
> Sqlite3 has been cycle-optimized for GCC. You
On 7/11/17, Jens Alfke <j...@mooseyard.com> wrote:
>
>> On Jul 11, 2017, at 10:35 AM, Richard Hipp <d...@sqlite.org> wrote:
>>
>> Generally speaking, FTS4 (and FTS3 and FTS5) requires no more than one
>> MATCH operator in the WHERE clause for each FTS4 ta
On 7/11/17, Jens Alfke <j...@mooseyard.com> wrote:
>
>> On Jul 11, 2017, at 10:35 AM, Richard Hipp <d...@sqlite.org> wrote:
>>
>> Generally speaking, FTS4 (and FTS3 and FTS5) requires no more than one
>> MATCH operator in the WHERE clause for each FTS4 ta
the FROM
clause, and that one MATCH operator must be a conjunct.
Sometimes you can bend this rule some and the query planner will still
be able to figure out what to do, but it is easy to bend it too far
and run into the error you encountered.
--
D. Richard Hipp
ator using the
sqlite3InvalidFunction() functions
(https://www.sqlite.org/src/artifact/899d8f02?ln=748-768) and that
function throws an error, by design.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
to me. Thanks.
--
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
-Val FROM SRC LIMIT 18
)
SELECT substr(val,1,instr(val,'.')+3) FROM src;
--
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
virus
> _______
> 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
work."
>
Another way to express this rule-of-thumb: Move the query to the
data, not the data to the query.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cg
cycles
As you can see, the gcc-compiled binary of SQLite is 9% smaller and
12% faster than the icc-compiled binary. So, maybe the solution is to
just not use icc?
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
similarly. You can send me the listing directly to
the email below, or post it on the mailing list - whichever is easiest
for you.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists
rrent system is working much better, thank you.
--
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 encryption/
> decryption (SEE) ?
>
Running VACUUM should not make any difference.
I don't know what is causing your problem. We don't have enough
detail to trouble-shoot the application for you.
Can you send example code that causes the SQLITE_CORRUPT err
On 7/1/17, Even Rouault <even.roua...@spatialys.com> wrote:
> On samedi 1 juillet 2017 06:07:30 CEST Richard Hipp wrote:
>> I'm confused...
>>
>> Are you reporting that clusterfuzz found a bug in SQLite that was
>> fixed in version 3.17.0?
>
> Seth, I can
t. I'm guessing that probably the GDAL team would need
> help from the sqlite3 team to address the issue anyway. I'd rather not
> wait 90 days for the original clusterfuzz bug to be made public.
>
> I'm not subscribed to the list so I'd appreciate C
On 6/30/17, petern <peter.nichvolo...@gmail.com> wrote:
> sqlite3_value_type() definitely deserves at least one document sentence
The change at https://www.sqlite.org/src/info/0db20efe201736b3 will
appear in the next release.
--
D. Richard Hipp
d...@s
___
> 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
unusual thing are you doing that requires you to become an expert
on the arcane type-conversion rules of SQLite?
--
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.
And, yes, an SQLITE_MISUSE error code could possibly prevent your file
from being deleted later on.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/lis
n the
query "SELECT sql FROM stmts" and print out the results just prior to
calling sqlite3_close(). That will clearly show you which prepared
statements you have forgotten to finalize.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing lis
. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
king it a per-call option allows new code to use it safely, without
> impacting any other components that might be using the same database.
>
> On 6/26/17, 11:31 AM, "drhsql...@gmail.com on behalf of Richard Hipp"
> <drhsql...@gmail.com on behalf of d...@sqli
On 6/26/17, Peter da Silva <peter.dasi...@flightaware.com> wrote:
> On 6/26/17, 11:15 AM, "drhsql...@gmail.com on behalf of Richard Hipp"
> <drhsql...@gmail.com on behalf of d...@sqlite.org> wrote:
>> If you get the latest check-in (https://www.sqlite.org/src/in
or legacy
compatibility.
On 6/26/17, Peter da Silva <peter.dasi...@flightaware.com> wrote:
> On 6/26/17, 9:00 AM, "sqlite-users on behalf of Richard Hipp"
> <sqlite-users-boun...@mailinglists.sqlite.org on behalf of d...@sqlite.org>
> wrote:
>> The "db nul
nalyzed */"
> \
> ");"
>
>
>
>
>
> Paul
> www.sandersonforensics.com
> skype: r3scue193
> twitter: @sandersonforens
> Tel +44 (0)1326 572786
> http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit
> -For
1001 - 1100 of 6136 matches
Mail list logo