Other small ones from the Quirks page:
Section 2:
"to realize the SQLite is not intended as"
to realize [that] SQLite is not intended as
Section 3.2:
"SQLite as no DATETIME datatype."
SQLite [has] no DATETIME datatype
Section 5:
"Due to an historical oversight"
Due to [a] historical oversight
Section 6:
"each output row might be composed from two more more rows"
each output row might be composed from two [or] more rows
"then the one of the rows is chosen arbitrarily"
then one of the rows is chosen arbitrarily
Section 8:
"into bad habit of"
into [the] bad habit of
or into bad habit[s] of
(I always feel a little weird when pointing out typos as the meaning is usually
perfectly fine the way it is, it feels like I'm being overly critical, and I
worry my "corrections" are also not quite right)
-----Original Message-----
From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On Behalf Of
Don V Nielsen
Sent: Thursday, July 11, 2019 10:58 AM
To: General Discussion of SQLite Database <sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] Grammar police
Sorry. This was in the Quirks, Caveats page, #2.
On Thu, Jul 11, 2019 at 9:57 AM Don V Nielsen <donvniel...@gmail.com> wrote:
> " An application interact with the database engine using function calls,
> not be sending messages to a separate process or thread."
>
> "An applications [interacts] ..., [not by]...
>
>
>
_______________________________________________
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
