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
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
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
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.
>
Ye
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 i
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 i
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
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 Eng
te.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 ha
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
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 t
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, a
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 w
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".
Happ
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 Jag
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
16 matches
Mail list logo
