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 <donvnielsen at gmail.com> 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
