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 <scott at scottdoctor.com> 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 <jay at kreibi.ch> 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
