On Jul 11, 2019, at 10:41 AM, Richard Hipp wrote:
>
> Here in the Southeastern US (specifically in Charlotte, NC) we really
> do say "an historical oversight". If you said "a historical
> oversight", people would look at you funny.
… :)
___
On 2019-07-11 2:31 PM, Carl Edquist wrote:
Ginger tells me that "a historical" is technically correct,
AFAICT, "an historical" is correct iff the "h" in "historical" is silent.
Eg, "It's an 'istorical oversight to pronounce the 'h' in 'historical'."
From the New Oxford American Dictionary
Ginger tells me that "a historical" is technically correct,
AFAICT, "an historical" is correct iff the "h" in "historical" is silent.
Eg, "It's an 'istorical oversight to pronounce the 'h' in 'historical'."
On Thu, 11 Jul 2019, Richard Hipp wrote:
On 7/11/19, David Raymond wrote:
Section
On 7/11/19, David Raymond wrote:
> I don't think I'd ever seen the quirks page
> (https://sqlite.org/quirks.html) before. Is that new-ish?
It's been around for a little more than a year. See
https://www.sqlite.org/docsrc/finfo?ss=c=pages%2Fquirks.in
--
D. Richard Hipp
d...@sqlite.org
And there was great rejoicing:
"1. Added the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to
sqlite3_db_config() for activating and deactivating the double-quoted string
literal misfeature. Both default to "on" for legacy compatibility, but
developers are encouraged to turn them
On 7/11/19, David Raymond wrote:
> I don't see [quirks.html]
> anywhere on https://sqlite.org/docs.html , maybe add it to the "Overview
> Documents" section?
The quirks.html document is now linked in the Overview Documents section.
https://www.sqlite.org/quirks.html
EVERYONE: If you have
Typos \ suggested amendments to quirks.html
Section 2
"When ever comparing SQLite to other SQL database engines"
When ever should be one word. "Whenever comparing SQLite to other SQL
database engines"
"An application interact with the database engine"
should be, "An application *interacts* with
On 11 Jul 2019, at 3:21pm, Richard Hipp wrote:
> EVERYONE: If you have personally experienced some unusual or
> unexpected feature of SQLite that you think should be added to
> "quirks.html", please follow-up to this thread, or send me private
> email, so that I can consider adding it.
A)
" 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
On Thu, Jul 11, 2019 at 6:47 AM Simon Slavin wrote:
>
> On 11 Jul 2019, at 3:21pm, Richard Hipp wrote:
>
> > EVERYONE: If you have personally experienced some unusual or
> > unexpected feature of SQLite that you think should be added to
> > "quirks.html", please follow-up to this thread, or
I'm using SQLITE3 (V3.29.0) on an arm embedded linux (2.6.39) on an ext3
filesystem.
Several processes hold the DB open and the "-wal" and "-shm" files exist.
if I use 'lsof | fgrep ' I can see all processes having all
three
files open. At least one of the processes uses threads, but every
On Thu, 11 Jul 2019 10:21:10 -0400
Richard Hipp wrote:
> If you have personally experienced some unusual or unexpected feature
> of SQLite that you think should be added to "quirks.html", please
> follow-up to this thread
Thank you for publishing this page. I would suggest these additions:
1.
Sorry. This was in the Quirks, Caveats page, #2.
On Thu, Jul 11, 2019 at 9:57 AM Don V Nielsen 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]...
>
>
>
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
On 7/11/19, David Raymond wrote:
> Section 5:
> "Due to an historical oversight"
> Due to [a] historical oversight
>
Here in the Southeastern US (specifically in Charlotte, NC) we really
do say "an historical oversight". If you said "a historical
oversight", people would look at you funny.
On 7/11/19, David Raymond wrote:
> Section 5:
> "Due to an historical oversight"
> Due to [a] historical oversight
>
Here in the Southeastern US (specifically in Charlotte, NC) we really
do say "an historical oversight". If you said "a historical
oversight", people would look at you funny.
On 7/11/19 3:45 PM, Ned Fleming wrote:
> On 2019-07-11 2:31 PM, Carl Edquist wrote:
>>> Ginger tells me that "a historical" is technically correct,
>>
>> AFAICT, "an historical" is correct iff the "h" in "historical" is
>> silent.
>>
>> Eg, "It's an 'istorical oversight to pronounce the 'h' in
17 matches
Mail list logo
