News for hackers. Stuff that matters.
Re:An SQL Solution for Jupyter by plumsempy on Tuesday February 09, 2021 @07:13PM (#26084309)
I know you pronounce it ES-KYU-EL because you used "an"
Re:An SQL Solution for Jupyter by fulafel on Wednesday February 10, 2021 @12:33AM (#26085997)
It's more common than "sequel" in non english speaking places IME.
Re:An SQL Solution for Jupyter by KerryJones on Tuesday February 09, 2021 @08:29PM (#26084812)
Yep, it through me off, I saw it somewhere years ago that the pronunciations were:

SQL = SEE-KWUHL MySQL = MY-ES-KYU-EL

And it's now engrained in my mind and this title through me off ;)

Re:An SQL Solution for Jupyter by junon on Tuesday February 09, 2021 @11:48PM (#26085831)
"An SQL", "through me off"....

I just woke up and my head is already spinning. ;)

Re:An SQL Solution for Jupyter by KerryJones on Wednesday February 10, 2021 @12:24AM (#26085957)
Oh boy, I think I need to go back to bed
Re:An SQL Solution for Jupyter by jessikat on Tuesday February 09, 2021 @09:56PM (#26085288)
"SEE-KWUHL" is actually the pronunciation for MS SQL Server. "ES-KYU-EL" is for all other uses of SQL.
Re:An SQL Solution for Jupyter by adolph on Tuesday February 09, 2021 @11:33PM (#26085775)
When SQL was established in the early 70s, it was called SEQUEL (Structured English Query Language). However, due to a copyright issue, it was changed it to SQL. In fact, SQL is typically pronounced “sequel” today, but some favor the non-acronym pronunciation of “ess-cue-el” (in case you didn’t know, an acronym is an abbreviation you can pronounce like a word, e.g. SQL or ANSI).

Read more at the ANSI Blog: The SQL Standard – ISO/IEC 9075:2016 (ANSI X3.135) https://blog.ansi.org/?p=158690

Re:An SQL Solution for Jupyter by slt2021 on Wednesday February 10, 2021 @01:07PM (#26092676)
sir, it is my-ass-que-el