[sqlite] website documentation wording
On 5/12/2015 2:08 AM, Keith Medcalf wrote: > Well, a Gartner Report paid for by Microsoft, which said that if you > pronounced it "ess queue ell" you were labelling yourself as a professional > programmer who understood relational database technologies, had probably used > them since the 1970's or before, and belonged in a dinosaur pen. > > On the other hand, the modern "buzzword compliant" pronunciation for "mere > coders" that had no knowledge of how relational database systems worked and > could not distinguish Boyce-Codd Normal Form from an Eggplant was "sequel". Well, at least as far as SQLite goes, I think this settles it unambiguously for me: https://www.youtube.com/watch?v=giAMt8Tj-84 Best Regards, Mohit.
[sqlite] website documentation wording
On 12 Dec 2015, at 6:19pm, Mohit Sindhwani wrote: > Well, at least as far as SQLite goes, I think this settles it unambiguously > for me: > https://www.youtube.com/watch?v=giAMt8Tj-84 "As soon as I have a person need for Foreign Keys I'm sure you'll see them come in pretty quick." -- Richard Hipp, 2007. Simon.
[sqlite] website documentation wording
On Fri, 04 Dec 2015 18:46:27 +, Keith Medcalf wrote: > > Intel's Management has decided -- for the imperfect tense. > Intel's Managemant have decided -- for the past perfect tense. Eh? These examples show the same tense. Niall O'Reilly
[sqlite] website documentation wording
On Sun, Dec 6, 2015 at 4:39 PM, Niall O'Reilly wrote: > On Fri, 04 Dec 2015 18:46:27 +, > Keith Medcalf wrote: >> >> Intel's Management has decided -- for the imperfect tense. >> Intel's Managemant have decided -- for the past perfect tense. > > Eh? These examples show the same tense. > Yes, that is true. Also, there is a typo in the second line. They just present different agreements. I believe both are grammatically correct. However, they differ in meaning, as the first one treats management as a single unit and the second one emphasizes that all managers decided something. -- Bernardo Sulzbach
[sqlite] website documentation wording
On 04 Dec 2015 at 17:13, Simon Slavin wrote: > The worst one is the collective corporation. Is it "Intel has decided" or > "Intel have decided" ? Whichever one I write for whichever side of the > Atlantic, I get told off for getting it wrong. I go with the US version in this instance; Intel is a corporation. WRT SQL pronunciation: no-one here says "sequel", not me, not SWMBO, nor, AFAICT, the cat, although he hasn't actually ventured an opinion. There's a bloke tomorrow I could ask - he's selling us a pendulum wall clock with Westminster chimes. -- Cheers -- Tim
[sqlite] website documentation wording
On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: > It is actually in the ISO standard that the proper pronunciation is ?ess cue > ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. Unfortunately I work as a contractor and if I can pick up the client's pronunciation and copy it, the client likes me more. So I flip back and forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and lots of other computer-related terms, depends on who's paying me that month. The worst one is the collective corporation. Is it "Intel has decided" or "Intel have decided" ? Whichever one I write for whichever side of the Atlantic, I get told off for getting it wrong. Simon.
[sqlite] website documentation wording
Agreed, almost everyone around here says "sequel", too.
On Fri, Dec 4, 2015 at 1:53 PM, Don V Nielsen wrote:
> Tangeant off this note, kind of a history question. "an SQLite". I
> personally would write "a SQL" because it is "sequel" to me. When did
> SQL--sequel become SQL--ess queue ell? I always remember it as being
> sequel, and it rolls off the tongue easier. And as sequel, it would be "a
> SQLite".
>
> Happy Holidays, all.
> dvn
>
> On Thu, Dec 3, 2015 at 3:41 PM, Bernardo Sulzbach gmail.com
>> wrote:
>
>> Good catch, Dirk
>>
>> On Thu, Dec 3, 2015 at 4:47 PM, Dirk Jagdmann wrote:
>> > I'm currently looking at https://www.sqlite.org/autoinc.html
>> >
>> > I suggest you change "You can access the ROWID of an SQLite table using
>> > one {of} the special column names..." and insert the word "of".
>> >
>> > --
>> > ---> Dirk Jagdmann
>> > > http://cubic.org/~doj
>> > -> http://llg.cubic.org
>> > ___
>> > sqlite-users mailing list
>> > sqlite-users at mailinglists.sqlite.org
>> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>>
>>
>> --
>> Bernardo Sulzbach
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
--
Bernardo Sulzbach
[sqlite] website documentation wording
I?d rather be a dinosaur with a clue, then buzzword compliant whipper-snapper. The amusing thing is if you?re really been doing databases since the early 1970s, you likely do call it ?sequel,? since that is what IBM actually called the first relational database language (SEQUEL - Structured English QUEry Language), but it was changed to SQL right before launch due to trademark issues. My guess is, at the time, "ess-cue-ell,? was preferred since there was a need to differentiate it from the existing trademark. -j, who had Eggplant Normal Form (baked) for lunch today On Dec 4, 2015, at 12:08 PM, Keith Medcalf wrote: > > Well, a Gartner Report paid for by Microsoft, which said that if you > pronounced it "ess queue ell" you were labelling yourself as a professional > programmer who understood relational database technologies, had probably used > them since the 1970's or before, and belonged in a dinosaur pen. > > On the other hand, the modern "buzzword compliant" pronunciation for "mere > coders" that had no knowledge of how relational database systems worked and > could not distinguish Boyce-Codd Normal Form from an Eggplant was "sequel". > >> It is actually in the ISO standard that the proper pronunciation is "ess >> cue ell". It became "sequel" in some circles, mostly thanks to Microsoft. >> >> The "Using SQLite" O'Reilly book also uses "an" (e.g. "an SQL statement") >> for the same reasons. >> >> -j >> >> >> On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: >> >>> Tangeant off this note, kind of a history question. "an SQLite". I >>> personally would write "a SQL" because it is "sequel" to me. When did >>> SQL--sequel become SQL--ess queue ell? I always remember it as being >>> sequel, and it rolls off the tongue easier. And as sequel, it would be >> "a >>> SQLite". >>> >>> Happy Holidays, all. >>> dvn >>> >> >> -- >> Jay A. Kreibich < J A Y @ K R E I B I.C H > >> >> "Intelligence is like underwear: it is important that you have it, but >> showing it to the wrong people has the tendency to make them feel >> uncomfortable." -- Angela Johnson >> >> >> >> >> >> ___ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
[sqlite] website documentation wording
Intel is a Corporation. Intel cannot, as a matter of fact and law, anywhere on the planet, decide anything. On the other hand, Intel's Management can make decisions. Therefore the correct statements are: Intel's Management has decided -- for the imperfect tense. Intel's Managemant have decided -- for the past perfect tense. To imply that a corporation has a power to do something which it cannot is simply sloppy writing. > -Original Message- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Tim Streater > Sent: Friday, 4 December, 2015 11:40 > To: SQLite mailing list > Subject: Re: [sqlite] website documentation wording > > On 04 Dec 2015 at 17:13, Simon Slavin wrote: > > > The worst one is the collective corporation. Is it "Intel has decided" > or > > "Intel have decided" ? Whichever one I write for whichever side of the > > Atlantic, I get told off for getting it wrong. > > I go with the US version in this instance; Intel is a corporation. > > WRT SQL pronunciation: no-one here says "sequel", not me, not SWMBO, nor, > AFAICT, the cat, although he hasn't actually ventured an opinion. There's > a bloke tomorrow I could ask - he's selling us a pendulum wall clock with > Westminster chimes. > > -- > Cheers -- Tim
[sqlite] website documentation wording
I much prefer S Q L to SEQUEL, but that annoyance is nothing compare to saying "SPROC" vs "stored procedure". Not sure quite *why* that bothers me so, but it does. Or rather did: My current job isn't in a predominantly database driven environment so I haven't had to listen to a lot of SQL lingo for 4.5 years or so. :) On Fri, Dec 4, 2015 at 11:10 AM, Scott Doctor wrote: > > Simply "Intel decided". using 'have', 'has', 'has been', 'have been' can > almost always be dropped entirely or replaced with 'is', 'was', 'were' > depending on tense. > > > Scott Doctor > scott at scottdoctor.com > -- > > > On 12/4/2015 9:13 AM, Simon Slavin wrote: > >> On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: >> >> It is actually in the ISO standard that the proper pronunciation is ?ess >>> cue ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. >>> >> Unfortunately I work as a contractor and if I can pick up the client's >> pronunciation and copy it, the client likes me more. So I flip back and >> forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and >> lots of other computer-related terms, depends on who's paying me that month. >> >> The worst one is the collective corporation. Is it "Intel has decided" >> or "Intel have decided" ? Whichever one I write for whichever side of the >> Atlantic, I get told off for getting it wrong. >> >> Simon. >> ___ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> >> >> > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison
[sqlite] website documentation wording
Well, a Gartner Report paid for by Microsoft, which said that if you pronounced it "ess queue ell" you were labelling yourself as a professional programmer who understood relational database technologies, had probably used them since the 1970's or before, and belonged in a dinosaur pen. On the other hand, the modern "buzzword compliant" pronunciation for "mere coders" that had no knowledge of how relational database systems worked and could not distinguish Boyce-Codd Normal Form from an Eggplant was "sequel". > It is actually in the ISO standard that the proper pronunciation is "ess > cue ell". It became "sequel" in some circles, mostly thanks to Microsoft. > > The "Using SQLite" O'Reilly book also uses "an" (e.g. "an SQL statement") > for the same reasons. > > -j > > > On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: > > > Tangeant off this note, kind of a history question. "an SQLite". I > > personally would write "a SQL" because it is "sequel" to me. When did > > SQL--sequel become SQL--ess queue ell? I always remember it as being > > sequel, and it rolls off the tongue easier. And as sequel, it would be > "a > > SQLite". > > > > Happy Holidays, all. > > dvn > > > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Intelligence is like underwear: it is important that you have it, but > showing it to the wrong people has the tendency to make them feel > uncomfortable." -- Angela Johnson > > > > > > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] website documentation wording
Simply "Intel decided". using 'have', 'has', 'has been', 'have been' can almost always be dropped entirely or replaced with 'is', 'was', 'were' depending on tense. Scott Doctor scott at scottdoctor.com -- On 12/4/2015 9:13 AM, Simon Slavin wrote: > On 4 Dec 2015, at 3:59pm, Jay Kreibich wrote: > >> It is actually in the ISO standard that the proper pronunciation is ?ess cue >> ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. > Unfortunately I work as a contractor and if I can pick up the client's > pronunciation and copy it, the client likes me more. So I flip back and > forth between 'an ess cue ell' and 'a sequel'. My opinion on that, and lots > of other computer-related terms, depends on who's paying me that month. > > The worst one is the collective corporation. Is it "Intel has decided" or > "Intel have decided" ? Whichever one I write for whichever side of the > Atlantic, I get told off for getting it wrong. > > Simon. > ___ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > >
[sqlite] website documentation wording
It is actually in the ISO standard that the proper pronunciation is ?ess cue ell?. It became ?sequel? in some circles, mostly thanks to Microsoft. The ?Using SQLite? O?Reilly book also uses ?an? (e.g. ?an SQL statement?) for the same reasons. -j On Dec 4, 2015, at 9:53 AM, Don V Nielsen wrote: > Tangeant off this note, kind of a history question. "an SQLite". I > personally would write "a SQL" because it is "sequel" to me. When did > SQL--sequel become SQL--ess queue ell? I always remember it as being > sequel, and it rolls off the tongue easier. And as sequel, it would be "a > SQLite". > > Happy Holidays, all. > dvn > -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
[sqlite] website documentation wording
Tangeant off this note, kind of a history question. "an SQLite". I
personally would write "a SQL" because it is "sequel" to me. When did
SQL--sequel become SQL--ess queue ell? I always remember it as being
sequel, and it rolls off the tongue easier. And as sequel, it would be "a
SQLite".
Happy Holidays, all.
dvn
On Thu, Dec 3, 2015 at 3:41 PM, Bernardo Sulzbach wrote:
> Good catch, Dirk
>
> On Thu, Dec 3, 2015 at 4:47 PM, Dirk Jagdmann wrote:
> > I'm currently looking at https://www.sqlite.org/autoinc.html
> >
> > I suggest you change "You can access the ROWID of an SQLite table using
> > one {of} the special column names..." and insert the word "of".
> >
> > --
> > ---> Dirk Jagdmann
> > > http://cubic.org/~doj
> > -> http://llg.cubic.org
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>
>
> --
> Bernardo Sulzbach
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
[sqlite] website documentation wording
Good catch, Dirk
On Thu, Dec 3, 2015 at 4:47 PM, Dirk Jagdmann wrote:
> I'm currently looking at https://www.sqlite.org/autoinc.html
>
> I suggest you change "You can access the ROWID of an SQLite table using
> one {of} the special column names..." and insert the word "of".
>
> --
> ---> Dirk Jagdmann
> > http://cubic.org/~doj
> -> http://llg.cubic.org
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
--
Bernardo Sulzbach
[sqlite] website documentation wording
I'm currently looking at https://www.sqlite.org/autoinc.html
I suggest you change "You can access the ROWID of an SQLite table using
one {of} the special column names..." and insert the word "of".
--
---> Dirk Jagdmann
> http://cubic.org/~doj
-> http://llg.cubic.org
