[sqlite] Documentation inconsistency

From here: https://www.sqlite.org/faq.html#q5 > (16) Why does ROUND(9.95,1) return 9.9 instead of 10.0? Shouldn't 9.95 round > up? This example seems to be no longer valid. Although the explanation is still valid in general, the particular example “SELECT ROUND(9.95,1)” actually returns 10.0

[sqlite] Documentation error

The page https://sqlite.org/src/doc/begin-concurrent/doc/begin_concurrent.md contains raw html: INSERT INTO t1(b) VALUES(); -- Mark Lawrence ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.o

Re: [sqlite] Documentation improvement request

On Feb 8, 2020, at 11:56 AM, Simon Slavin wrote: > > ? I don't know whether this can be done automatically. Possibly for any > page which has section headers. Yes, it can be done, and I’ve lined out several options for doing so here: https://www.fossil-scm.org/forum/forumpost/a5e1391eb3

[sqlite] Documentation improvement request

Some pages in the documentation started small but had stuff gradually added to them over the years. For the pages can a "Table Of Contents" be added at the top, like the one on

[sqlite] Documentation issues for collating sequences

I encountered a documentation issue at the page that describes how to define new collating sequences ( https://www.sqlite.org/c3ref/create_collation.html ) For the 3 variants of sqlite3_create_collation the 5th argument is a function called "xCompare", but the text refers to "xCallback" instead

[sqlite] Documentation Bug

The documentation at https://sqlite.org/quirks.html#no_separate_datetime_datatype refers to ISO 8610. I should be ISO 8601. Best Regards, Mark -- Mark Simon Manngo Net Pty Ltd mobile:0411 246 672 email:m...@manngo.net web:http://www.manngo.net Resume:http://

[sqlite] Documentation issue: carray

Hello, on the page https://www.sqlite.org/carray.html This query gives the same result: --> This query gives the same results, uniquely ordered. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org htt

Re: [sqlite] Documentation bug: CREATE TABLE diagram misplaces comma

On Wed, 18 Sep 2019 17:59:46 +, David Raymond wrote: > It is comma then table-constraint. Check the direction of the arrow > on that loop. Ah! Sorry for the noise, I missed the direction. - Tim ___ sqlite-users mailing list sqlite-users@mailinglist

Re: [sqlite] Documentation bug: CREATE TABLE diagram misplaces comma

- From: sqlite-users On Behalf Of Tim McCormack Sent: Wednesday, September 18, 2019 9:14 AM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] Documentation bug: CREATE TABLE diagram misplaces comma In https://www.sqlite.org/lang_createtable.html the diagram for create-table-stmt

[sqlite] Documentation bug: CREATE TABLE diagram misplaces comma

In https://www.sqlite.org/lang_createtable.html the diagram for create-table-stmt contains a parenthesized list of column-def and table-constraint, which I'll represent in a pseudo-grammar here: "(" ("," )* ( ",")* ")" However, that would forbid (foo, bar, PRIMARY_KEY foo) and require instead so

[sqlite] Documentation error in comment in carray.c

There's a mistake in the documentation block-comment at the start of carray.c: **sqlite3_bind_value(pStmt, i, aX, "carray", 0); The function should be sqlite3_bind_pointer. —Jens ___ sqlite-users mailing list sqlite-users@mailinglists.sqlit

[sqlite] Documentation addition request for FTS3 / FTS4 phrase search

Hi, please add to the documentation that column limited phrase search is not supported by FTS3 and FTS4. Example: CREATE VIRTUAL TABLE FTSTable USING FTS3 (content,body); SELECT * FROM FTSTable WHERE FTSTable MATCH 'content:"one two"'; Does not result in an error but also returns no results.

Re: [sqlite] Documentation misunderstanding or bug (FTS3 and "^" character)?

Hi, yes, but unfortunately I have still a project using FTS3 tables to which I have to add new features.. Regards, Hardy > Am 2019-08-30 um 13:00 schrieb Dan Kennedy : > > > On 30/8/62 17:39, mailing lists wrote: >> Hi, >> >> but there is no token '^beta'! Even if in FTS3 '^' is not regarded

Re: [sqlite] Documentation misunderstanding or bug (FTS3 and "^" character)?

On 30/8/62 17:39, mailing lists wrote: Hi, but there is no token '^beta'! Even if in FTS3 '^' is not regarded as a special character. Is the '^' removed by the tokenizer? Right. It's removed by the tokenizer. FTS3/4 is focused on backwards compatibility. New work should really use FTS5 - i

Re: [sqlite] Documentation misunderstanding or bug (FTS3 and "^" character)?

Hi, but there is no token '^beta'! Even if in FTS3 '^' is not regarded as a special character. Is the '^' removed by the tokenizer? Because it is regarded as a diacritical character? PS: I have to admit that I have overlooked the comment that '^' works only for FTS4 tables. Regards, Hardy >

Re: [sqlite] Documentation misunderstanding or bug (FTS3 and "^" character)?

The fts3/4 documentation says: "If the FTS table is an FTS4 table (not FTS3), a token may also be prefixed with a "^" character. In this case, in order to match the token must appear as the very first token in any column of the matching row." So change "FTS3" to "FTS4" and it will likely wo

[sqlite] Documentation misunderstanding or bug (FTS3 and "^" character)?

Hi, I could not find an example showing a result in the documentation, therefore I created one by myself: CREATE VIRTUAL TABLE myData USING FTS3(content); INSERT INTO myData 'alpha beta'; 1) SELECT * FROM myData WHERE myData MATCH 'beta'; Result: content alpha beta This is what I expected.

Re: [sqlite] Documentation update request

Kevin Benson, on Thursday, August 15, 2019 02:40 PM, wrote... > > On Thu, Aug 15, 2019 at 2:33 PM Jose Isaias Cabrera, on > wrote: > > Oh! Trickery! > > > > > Dickery (sometimes a nickname for RICHARD ;-) > Doc (...umentation; the something Richard "Dick" Hipp was doing ;-) I could never use tho

Re: [sqlite] Documentation update request

On Thu, Aug 15, 2019 at 2:33 PM Jose Isaias Cabrera wrote: > Richard Hipp, on Thursday, August 15, 2019 01:32 PM, wrote... > > > > On 8/15/19, Simon Slavin, on > > > On 15 Aug 2019, at 5:20pm, Richard Damon, on > > > > > >> You under quote, the faq says it “can not be changed (except under > > >>

Re: [sqlite] Documentation update request

Richard Hipp, on Thursday, August 15, 2019 01:32 PM, wrote... > > On 8/15/19, Simon Slavin, on > > On 15 Aug 2019, at 5:20pm, Richard Damon, on > > > >> You under quote, the faq says it “can not be changed (except under > >> extra-ordinary conditions).”, and those extra-ordinary conditions are a >

Re: [sqlite] Documentation update request

On 8/15/19, Simon Slavin wrote: > On 15 Aug 2019, at 5:20pm, Richard Damon wrote: > >> You under quote, the faq says it “can not be changed (except under >> extra-ordinary conditions).”, and those extra-ordinary conditions are a >> link to the second section you mention. > > I didn't notice that,

Re: [sqlite] Documentation update request

On 15 Aug 2019, at 5:20pm, Richard Damon wrote: > You under quote, the faq says it “can not be changed (except under > extra-ordinary conditions).”, and those extra-ordinary conditions are a link > to the second section you mention. I didn't notice that, for some reason. Thanks for the correc

Re: [sqlite] Documentation update request

> On Aug 15, 2019, at 10:37 AM, Simon Slavin wrote: > > > > says that sqlite_master cannot be changed. > > > > tells you how to change it. > You under quote, the faq says it “can not be changed (except

[sqlite] Documentation update request

says that sqlite_master cannot be changed. tells you how to change it. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlit

Re: [sqlite] Documentation correction

On the heel of Tom's input is the fragment " then that name always refers the explicitly declared column". Should that be " then that name always refers *to* the explicitly declared column"? On Mon, Apr 15, 2019 at 3:32 PM wrote: > Hi, I just wanted to point out a minor discrepancy in the docs b

[sqlite] Documentation correction

Hi, I just wanted to point out a minor discrepancy in the docs below. https://www.sqlite.org/lang_createtable.html#rowid where it says: If a table contains a user defined column named "rowid", "oid" or "_rowid_", then that name always refers the explicitly declared column and cannot be used to

[sqlite] Documentation enhancement request: VACUUM

The documentation for VACUUM says "A VACUUM will fail if there is an open transaction" Could this statement be changed to make it clear whether this refers to other connections having an open transaction, and whether it means that VACUUM fill fail if it itself is inside a transaction ? I seem

[sqlite] Documentation error: USE_ZLIB versus HAVE_ZLIB

Good morning! Both https://sqlite.org/cli.html#_do_it_yourself_builds_ and https://sqlite.org/compile.html#use_zlib mention option SQLITE_USE_ZLIB to enable _zipfile and _sqlar. However, shell.c.in uses SQLITE_HAVE_ZLIB for this. I think this is a documentation error. checkout: 7a0a26ed3

[sqlite] Documentation change request

talks about PRAGMA read_uncommitted = boolean; Explicitly stating that the argument should be boolean. However the explanation of the effect of the PRAGMA talks about its argument as if it is SERIALIZABLE. No boolean value to indicate

Re: [sqlite] Documentation is lying to me

g at 3.26.0 >> >> >> >> -Original Message- >> From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org >> <mailto:sqlite-users-boun...@mailinglists.sqlite.org>] On Behalf Of Joshua >> Wise >> Sent: Wednesday, February 27, 2019

Re: [sqlite] Documentation is lying to me

; <mailto:sqlite-users-boun...@mailinglists.sqlite.org>] On Behalf Of Joshua > Wise > Sent: Wednesday, February 27, 2019 2:13 PM > To: SQLite mailing list > Subject: Re: [sqlite] Documentation is lying to me > > I can confirm that it also doesn’t work with SQLite version 3.24.0

Re: [sqlite] Documentation is lying to me

nly a Stairway to Heaven says a >> lot about anticipated traffic volume. >> >>> -Original Message- >>> From: sqlite-users [mailto:sqlite-users- >>> boun...@mailinglists.sqlite.org <mailto:boun...@mailinglists.sqlite.org>] >>> On Behalf Of

Re: [sqlite] Documentation is lying to me

says a >> lot about anticipated traffic volume. >> >>> -Original Message- >>> From: sqlite-users [mailto:sqlite-users- >>> boun...@mailinglists.sqlite.org <mailto:boun...@mailinglists.sqlite.org>] >>> On Behalf Of Joshua Thomas Wi

Re: [sqlite] Documentation is lying to me

database_list; > > select * from pragma_database_list(); > > > --- > 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-user

Re: [sqlite] Documentation is lying to me

On 27/2/19 10:06 AM, Joshua Thomas Wise wrote: > In this SQLite3 documentation (https://www.sqlite.org/pragma.html#pragfunc), > it says that information_schema could be implemented by doing something like > this: > > ATTACH ':memory:' AS 'information_schema'; > CREATE VIEW information_schema.sche

Re: [sqlite] Documentation is lying to me

f Of Joshua Thomas Wise >Sent: Tuesday, 26 February, 2019 19:06 >To: sqlite-users@mailinglists.sqlite.org >Subject: [sqlite] Documentation is lying to me > >In this SQLite3 documentation >(https://www.sqlite.org/pragma.html#pragfunc), it says that >information_schema could be impl

[sqlite] Documentation is lying to me

In this SQLite3 documentation (https://www.sqlite.org/pragma.html#pragfunc), it says that information_schema could be implemented by doing something like this: ATTACH ':memory:' AS 'information_schema'; CREATE VIEW information_schema.schemata(schema_name) AS SELECT name FROM pragma_database_list(

Re: [sqlite] Documentation error

On 1/2/19, Joe Jacobs wrote: > > Long story short is that this may be i'm using an old version of sqlite > lite and the command has changed. > Yes. Since 2013-05-20, there have been 73 releases and 10167 distinct changes. One of those 10167 changes was this: https://www.sqlite.org/src/timeline

[sqlite] Documentation error

I think this is an error in the command line documentation or room for minor improvement. I was reading through the docs trying to learn about the command line tool and ran into a snag, so i thought i'd report it. https://www.sqlite.org/cli.html In section 3 where it talks about dot commands and

Re: [sqlite] Documentation wording problem

Fixed now. Thanks. On 11/24/18, Project Nayuki wrote: > In the SQLite online documentation, there seems to be a problem in the > wording of a sentence, which I highlighted in angle brackets. > > https://www.sqlite.org/wal.html > Write-Ahead Logging > 5. Read-Only Databases > > "Even though it is

[sqlite] Documentation wording problem

In the SQLite online documentation, there seems to be a problem in the wording of a sentence, which I highlighted in angle brackets. https://www.sqlite.org/wal.html Write-Ahead Logging 5. Read-Only Databases "Even though it is possible to open a read-only WAL-mode database, is good practice is

Re: [sqlite] Documentation of SQLite

On 11/10/2018 05:44 PM, Patrik Nilsson wrote: Dear All, Where can I find the downloadable HTML documentation? Not so long ago I could download it on the download page. It was forgotten for the 3.25.3 release. It's back up now. Dan. ___ sqlite-users

[sqlite] Documentation of SQLite

Dear All, Where can I find the downloadable HTML documentation? Not so long ago I could download it on the download page. Best regards, Patrik -- PGP-key fingerprint: 1B30 7F61 AF9E 538A FCD6 2BE7 CED7 B0E4 3BF9 8D6C ___ sqlite-users mailing list

[sqlite] documentation for sqlite3_index_info-ídxStr typo.

https://www.sqlite.org/c3ref/index_info.html Instead of referring to idxStr there is text that talks about idxPtr. It should mention if idxStr must point to a valid string or can it point to arbitrary data. If the latter than idxStr type should change to void* perhaps. Reading this doc it sounds l

Re: [sqlite] Documentation Typo : https://sqlite.org/optoverview.html section 15

Fixed now. Tnx. On 4/12/18, Keith Medcalf wrote: > > https://sqlite.org/optoverview.html > > 15, the push down optimization. The BETWEEN clause is in error? > > SELECT x, y, b > FROM t2 > JOIN (SELECT DISTINCT a, b FROM t1 WHERE b BETWEEN 10 AND 20) > WHERE b BETWEEN 10 AND 10; > > should

[sqlite] Documentation Typo : https://sqlite.org/optoverview.html section 15

https://sqlite.org/optoverview.html 15, the push down optimization. The BETWEEN clause is in error? SELECT x, y, b FROM t2 JOIN (SELECT DISTINCT a, b FROM t1 WHERE b BETWEEN 10 AND 20) WHERE b BETWEEN 10 AND 10; should probably be BETWEEN 10 AND 20; --- The fact that there's a Highway to

Re: [sqlite] Documentation update

On 9 Apr 2018, at 11:02am, R Smith wrote: > If you prefer "different from" to "different to", it is simply likely that > you are American rather than English, in which language the preference (I > should say "habit" really) is "different to" rather than "different from", > but I gather from

Re: [sqlite] Documentation update

I'm adding to my bucket list meeting some of you in person. On Mon, Apr 9, 2018 at 5:58 AM, Niall O'Reilly wrote: > On 9 Apr 2018, at 11:02, R Smith wrote: > > > Gentlemen - shall we call pistols at dawn to settle this? > > Or my favourite duel: Face-pulling at midnight. :) > > 8-) > > /Niall

Re: [sqlite] Documentation update

On 9 Apr 2018, at 11:02, R Smith wrote: > Gentlemen - shall we call pistols at dawn to settle this? > Or my favourite duel:  Face-pulling at midnight.  :) 8-) /Niall signature.asc Description: OpenPGP digital signature ___ sqlite-users mailing list s

Re: [sqlite] Documentation update

t;different than" - which got criticized a lot by the old guard, but with no real grounds. The word "to" is a natural juxtaposition relation indicator. "A is next to B", "I prefer coconut to mango" and "Apples are crunchy compared to oranges". T

Re: [sqlite] Documentation update

On 9 Apr 2018, at 2:08, Simon Slavin wrote: > "In unique indices, each NULL value is considered different to every other > NULL value. Thus each NULL value is unique." For the sake of my late English teacher, I hope the revised document will read "... different __from__ ...". Best regards, Ni

Re: [sqlite] Documentation update

On 9 Apr 2018, at 1:08am, Don V Nielsen wrote: > "For the purposes of unique indices, all NULL values are considered [to] > different from all other NULL values and are thus unique." > > I think it should read "...NULL value are considered different..." > > https://www.sqlite.org/lang_createind

Re: [sqlite] Documentation update

"to be", or not "to be" :) On Sun, Apr 8, 2018 at 7:08 PM, Don V Nielsen wrote: > "For the purposes of unique indices, all NULL values are considered [to] > different from all other NULL values and are thus unique." > > I think it should read "...NULL value are considered different..." > > http

[sqlite] Documentation update

"For the purposes of unique indices, all NULL values are considered [to] different from all other NULL values and are thus unique." I think it should read "...NULL value are considered different..." https://www.sqlite.org/lang_createindex.html dvn ___

Re: [sqlite] Documentation Query/Correction

flt_value|pk 0|i|INT|0||0 1|nu|NUM|0||0 2|r|REAL|0||0 3|t|TEXT|0||0 4|b||0||0 5|n||0||0 -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of John McMahon Sent: Wednesday, April 04, 2018 3:54 PM To: SQLite Users Subject: [sqlite] Documentation Q

Re: [sqlite] Documentation Query/Correction

te.org] On Behalf Of John McMahon Sent: Wednesday, April 04, 2018 3:54 PM To: SQLite Users Subject: [sqlite] Documentation Query/Correction In documentation for version 3.21.0: in datatypes3.html ... 3. Type Affinity ... Each column in an SQLite 3 database is assigned one of the following type a

[sqlite] Documentation Query/Correction

In documentation for version 3.21.0: in datatypes3.html ... 3. Type Affinity ... Each column in an SQLite 3 database is assigned one of the following type affinities: TEXT NUMERIC INTEGER REAL BLOB (Historical note: The "BLOB" type affinity used to be called "NONE". But

Re: [sqlite] Documentation update 2

Thank YOU. Fix looks good now. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Documentation update

On 2018/01/31 3:13 PM, Simon Slavin wrote: I see. It has already been fixed. Sorry for the niggle. Simon. It's hard to stay on top of an error in the SQLite universe They disappear so darn quick. ___ sqlite-users mailing list sqlite-users@mailing

Re: [sqlite] Documentation update

On 31 Jan 2018, at 1:11pm, Kees Nuyt wrote: > On Wed, 31 Jan 2018 13:07:17 +, Simon Slavin > wrote: >> >> Can you clarify your correction ? I don't see a difference. > > It used to be: > 8.3. I/O while obtaining a lock leads to corruption > > (the word error is missing) I see. It has a

Re: [sqlite] Documentation update

On Wed, 31 Jan 2018 13:07:17 +, Simon Slavin wrote: > > >On 30 Jan 2018, at 6:51pm, William Entriken wrote: > >> Hello. Regarding https://www.sqlite.org/howtocorrupt.html, item 8.3. >> Perhaps this should be >> >>> 8.3. I/O error while obtaining a lock leads to corruption > > Can you clarif

Re: [sqlite] Documentation update

On 30 Jan 2018, at 6:51pm, William Entriken wrote: > Hello. Regarding https://www.sqlite.org/howtocorrupt.html, item 8.3. > Perhaps this should be > >> 8.3. I/O error while obtaining a lock leads to corruption Can you clarify your correction ? I don't see a difference. Simon. __

Re: [sqlite] Documentation update 2

Fixed now (I think). Thanks for the bug reports On 1/30/18, William Entriken wrote: > Hello again. Regarding https://www.sqlite.org/howtocorrupt.html, item 8.6. > Currently: > >> This race condition had apparently existing in all prior versions of > SQLite... > > Should be: > >> This race condit

[sqlite] Documentation update 2

Hello again. Regarding https://www.sqlite.org/howtocorrupt.html, item 8.6. Currently: > This race condition had apparently existing in all prior versions of SQLite... Should be: > This race condition had apparently existed in all prior versions of SQLite... Regards, William Entriken ___

[sqlite] Documentation update

Hello. Regarding https://www.sqlite.org/howtocorrupt.html, item 8.3. Perhaps this should be > 8.3. I/O error while obtaining a lock leads to corruption Regards, William Entriken ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://m

[sqlite] Documentation Bug?

Hello list, I believe there is a documentation bug in the docs describing the new zipfile feature: https://sqlite.org/zipfile.html In section 3.2.1. Adding Entries to a Zip Archive it reads, quote For example, to add a symbolic link from "link.txt" to "m.txt": INSERT INTO temp.zip(name, mode

[sqlite] documentation edits needed

Here are some suggested improvements for the constraints listed under:     https://www.sqlite.org/optoverview.html, section  10. Subquery flattening 3. The subquery is not the right operand of a LEFT JOIN then the subquery may not be a join, the FROM clause of the subquery may not contain

[sqlite] Documentation typo

In the following passage contains a typo ("crass" -> "crash"): Setting PRAGMA synchronous=OFF can cause the database to go corrupt if there is an operating-system crass or power failure... -- J. King __

[sqlite] Documentation improvement suggestion

I propose a change to this page: This sentence: "This document describes and defines the on-disk database file format used by SQLite." The sentence is correct but I’ve had at least one case where such a statement can cause a problem in future. Could "vers

Re: [sqlite] Documentation Error

https://www.sqlite.org/c3ref/open.html On Wed, Aug 23, 2017 at 10:29 PM, J Decker wrote: > > > If URI filename interpretation is > enabled, and the filename argument begins with "file:", then the filename > is interpreted as a URI. URI filename interpretation is

[sqlite] Documentation Error

If URI filename interpretation is enabled, and the filename argument begins with "file:", then the filename is interpreted as a URI. URI filename interpretation is enabled if the SQLITE_OPEN_URI flag is set in th

Re: [sqlite] Documentation improvement recommendations

Here's a couple more. On this page: https://www.sqlite.org/src/doc/trunk/README.md describes the LALR(1) grammer should be: describes the LALR(1) grammar Each has a suscinct should be: Each has a succinct - On this page: https://www.sqlite.org/dbstat.html The the DBSTAT virtual sh

[sqlite] Documentation improvement recommendations

Hi All, Here's a list of some documentation improvements. - On this page: https://www.sqlite.org/rbu.html an RBU Vaccum is should be: an RBU Vacuum is What about this change. Preparing An RBU Update File To: Preparing an RBU Update File Too many words: it may be be more shoul

[sqlite] documentation: add PRAGMA journal_mode form without schema

The pragma documentation for journal_mode forms all specify a schema: https://sqlite.org/pragma.html#pragma_journal_mode PRAGMA schema.journal_mode; PRAGMA schema.journal_mode = DELETE | TRUNCATE | PERSIST | MEMORY | WAL | OFF The WAL documentation uses a form without a schema: https://sqlite.o

[sqlite] documentation: typo in foreign keys section

https://sqlite.org/foreignkeys.html#fk_indexes There is a typo under Foreign Keys Section 3. Required and Suggested Database Indexes: "Foreign key DML errors are may be reported if:" Thank you for the excellent documentation. ___ sqlite-users mailing

Re: [sqlite] Documentation bug: lang_insert.html needs examples

Slavin > Sent: Saturday, 1 July, 2017 17:14 > To: SQLite mailing list > Subject: Re: [sqlite] Documentation bug: lang_insert.html needs examples > > > > On 2 Jul 2017, at 12:08am, 積丹尼 Dan Jacobson > wrote: > > > So near the top of the article add this synop

Re: [sqlite] Documentation bug: lang_insert.html needs examples

On 2 Jul 2017, at 12:08am, 積丹尼 Dan Jacobson wrote: > So near the top of the article add this synopsis of the three basic forms, > INSERT INTO moz_cookies VALUES(1,'Bart',12); > INSERT INTO moz_cookies SELECT . > INSERT INTO moz_cookies DEFAUT_VALUES ??? If those are "the" three forms,

[sqlite] Documentation bug: lang_insert.html needs examples

file:///usr/share/doc/sqlite3-doc/lang_insert.html says "The INSERT statement comes in three basic forms." OK, but you need to add examples of all three. E.g., you say "The first form (with the "VALUES" keyword)" well there is no example. So near the top of the article add this synopsis of the th

[sqlite] Documentation bug: cli.html#csv_import should warn about NULLs

sqlite3-doc/cli.html#csv_import should warn that there is no way to preserve NULL with CSV. You can even add a proof if you want, $ sqlite3 mydata.db

Re: [sqlite] Documentation bug: remove gmane address on Bug Report page

By the way, you might want to unlock http://mailinglists.sqlite.org/cgi-bin/mailman/private/sqlite-users/ as one can read it on Nabble anyway. Then you could just tell users to see the Archives. ___ sqlite-users mailing list sqlite-users@mailinglists.sqli

[sqlite] Documentation bug: remove gmane address on Bug Report page

Please fix https://www.sqlite.org/src/wiki?name=Bug+Reports . It says to see http://news.gmane.org/gmane.comp.db.sqlite.general but that page is no longer working. Maybe tell them to see http://sqlite.1065341.n5.nabble.com/ (But I don't know if that is the canonical URL.) __

Re: [sqlite] Documentation bug. Detecting NULL extension arguments.

On 6/30/17, petern 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...@sqlite.org ___ sqlite-users ma

Re: [sqlite] Documentation bug. Detecting NULL extension arguments.

Thank you for the quick reply. After reading your reply and grepping around for more examples containing sqlite3_type_value I see now the documentation gives the impression that return types only apply to sqlite3_value_numeric_type(). Had I clicked randomly on the link to https://sqlite.org/c3r

Re: [sqlite] Documentation bug. Detecting NULL extension arguments.

On 6/30/17, petern wrote: > Is this the recommended way for any argument type? > > zCol = (const char*)sqlite3_value_text(argv[i]); > if( 0==zCol ) return; No. What you have above detects out-of-memory errors when trying to convert an argument in some non-TEXT type in to TEXT, or when conver

[sqlite] Documentation bug. Detecting NULL extension arguments.

Is this the recommended way for any argument type? zCol = (const char*)sqlite3_value_text(argv[i]); if( 0==zCol ) return; Docs say protected_sqlite3_value can represent NULL but how is not explained anywhere. https://www.sqlite.org/c3ref/value_blob.html https://www.sqlite.org/c3ref/value.htm

Re: [sqlite] Minor typo in SQLite documentation

Fixed. Thanks. On 6/6/17, Leon Höpfl wrote: > Hello guys, > First of all, thanks for your great work, I really appreciate working > with SQLite. I've recently found a minor typo in > https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where > it states "it is exists, is simply igno

[sqlite] Minor typo in SQLite documentation

Hello guys, First of all, thanks for your great work, I really appreciate working with SQLite. I've recently found a minor typo in https://sqlite.org/fileformat2.html#sqlite_stat2 in the last row, where it states "it is exists, is simply ignored", maybe it should state "if it exists, is simply igno

Re: [sqlite] documentation flaws

On 6/2/17, Rob Golsteijn wrote: > > I found 2 flaws in the online documentation: > Should be fixed now. Thanks for the report. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sq

[sqlite] documentation flaws

Hi List, I found 2 flaws in the online documentation: Documentation conflict: Section "1.3. Limitations" on http://sqlite.org/sessionintro.html states: "• Prior to SQLite version 3.17.0, the session extension only worked with rowid tables, not WITHOUT RO

Re: [sqlite] Documentation of valid ORDER BY terms after UNION?

s the error you received. (Brain is melted at end of the day, so hopefully that all made a little sense. I'm sure someone can re-word that better than I just did.) -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of no...@null.net Se

Re: [sqlite] Documentation of valid ORDER BY terms after UNION?

On Mon May 15, 2017 at 09:58:31PM +0100, Simon Slavin wrote: > > On 15 May 2017, at 9:30pm, no...@null.net wrote: > > >SELECT > >1 AS col > >UNION ALL > >SELECT > >0 AS col > >ORDER BY > >col > 0 DESC; > > Out of interest, intuitively rather than reading d

Re: [sqlite] Documentation of valid ORDER BY terms after UNION?

On 15 May 2017, at 9:30pm, no...@null.net wrote: >SELECT >1 AS col >UNION ALL >SELECT >0 AS col >ORDER BY >col > 0 DESC; Out of interest, intuitively rather than reading documentation, which do you think should be done first ? Should SQL do both SELECTs

[sqlite] Documentation of valid ORDER BY terms after UNION?

This works: SELECT 1 AS col ORDER BY col > 0 DESC; The following fails with "Error: 1st ORDER BY term does not match any column in the result set." SELECT 1 AS col UNION ALL SELECT 0 AS col ORDER BY col > 0 DESC; I've read "The ORD

Re: [sqlite] Documentation error

On 2/15/17, Paul Sanderson wrote: > The process for calculating a checksum text on the SQLite file format page > contains two errors. > Thanks for spotting this. Should be fixed now. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sql

[sqlite] Documentation error

The process for calculating a checksum text on the SQLite file format page contains two errors. Currently reads: The checksum is an unsigned 32-bit integer computed as follows: 1. Initialize the checksum to the checksum nonce value found in the journal header at offset 12. 2. Initialize

[sqlite] Documentation change in 3.17.0

Hi, The diff from 3.16.2 -> 3.17.0 contains [[ ** table that is being modified. -** ^The sixth parameter to the preupdate callback is the initial [rowid] of the -** row being changes for SQLITE_UPDATE and SQLITE_DELETE changes and is -** undefined for SQLITE_INSERT changes. -** ^The sevent

Re: [sqlite] Documentation clarification request... (re: Triggers)

On 2 Feb 2017, at 2:38pm, Michael Tiernan wrote: > So that makes sense (I think) and isn't causing a problem for me but then, a > little further on it says: > > If a WHEN clause is supplied, the SQL statements specified are only > executed for rows for which the WHEN clause is true. If no

[sqlite] Documentation clarification request... (re: Triggers)

In the online documentation: https://sqlite.org/lang_createtrigger.html It says: At this time SQLite supports only FOR EACH ROW triggers, not FOR EACH STATEMENT triggers. Hence explicitly specifying FOR EACH ROW is optional. FOR EACH ROW implies that the SQL statements specified in t

Re: [sqlite] Documentation bug

On 7/28/16, Java4Life wrote: > Hi All, > > I think there is a comma missing here: > > Here: https://www.sqlite.org/fts3.html#section_4_2 Please confirm that the draft document for the next release (http://sqlite.org/draft/fts3.html#section_4_2) fixes the problem you see. Thanks. -- D. Richard

[sqlite] Documentation bug

Hi All, I think there is a comma missing here: Here: https://www.sqlite.org/fts3.html#section_4_2 ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

  1   2   3   4   >