Same Language, Different Words

  • Comments posted to this topic are about the item Same Language, Different Words

  • My experience with "same language, different words" was with an Oracle database. The SQL used to query Oracle is very similar to MS SQL, but not quite the same. Some queries worked fine in both languages, but then you'd add in some LEFT JOINS and the syntax felt more like the SQL syntax I used back in the 90s ( using *= for the joins and the ON clause items in the WHERE clause instead of next to the tables being joined ~ wheeee!)

  • The news about PostgreSQL taking #1 here is not as astounding when considering StackOverflow breaking out MariaDB into a separate choice. I'd argue that MySQL/MariaDB are effectively the same choice to the average respondent developer and would still be on top if combined. That said, the trend certainly favors PostgreSQL, which grew by 2%, vs. the combined (MySQL+MariaDB), which dropped by 6%, in comparing the same survey from 2022 to 2023.

  • 'A common people, divided by a common language...' (to paraphrase W. Churchill, quite possibly quoting someone else)

    I noticed this in Japan when I was there on the JET Programme. I had fewer misunderstandings with Japanese people because when I didn't know what they were saying, I asked. I am from Ireland. I thought that I understood what Americans meant when they spoke. It turns out that I just knew the words and some of them had other meanings.

    The only one that I really remember is 'to be done with' means to be finished. I was confused when I was if I was done with that. But then, the verb 'to do' does a lot of heavy lifting in the various flavours of English. Which, thanks to Microsoft & Apple, are disappearing.

  • This was removed by the editor as SPAM

  • I've recently been using Snowflake and the SQL there is very similar, but not quite the same. The main problem I have is not with the flavour of SQL, but the fact that there isn't a find/replace option in the worksheets (or, if there is, I haven't found it) and there's no equivalent of my favourite SSMS add-in to provide intellisense and code formatting. Coding is much slower as a result.

  • Thanks for the reply, Chris. That favorite little plugin has been helpful to so many, for sure. There's always some level of discussion around how it could be done across multiple databases because the toolset/IDE landscape starts to get pretty wide and diverse. But it's good to hear that it continues to provide value!

    You've touched on something that, just thinking about it for 30 seconds, might be a good place for AI assistance at some point. Current attempts have been clunky (and often not correct), but having a translation tool that can help with those "find and replace" opportunities in our queries could be interesting, for sure! 🤔

     

    Cheers!

  • 👋 @LadyRuna! Thanks for sharing. The syntax nuances definitely keep us on our toes, and often have historical baggage associated with those unique implementations. It can be amusing at times (at least after we learn how to do it) to see how it all fits together.

    Cheers!

  • @tomwillwerth - really good catch. I hadn't dug much further between the two years and I agree that the change is noteworthy! Regardless, it's clear that data and databases continue to be central and important to the daily life of developers. 🎉

    Cheers!

  • @sean-redmond, thanks for the reply. I couldn't agree more. Asking is usually the best path forward. It builds relationship and helps others see where the shortcomings in knowledge sharing are (docs, blogs, etc.). Unfortunately, I can't help "to do" more about the (sometimes) brokenness of English. 😂

  • Ryan Booz wrote:

    @sean-redmond, thanks for the reply. I couldn't agree more. Asking is usually the best path forward. It builds relationship and helps others see where the shortcomings in knowledge sharing are (docs, blogs, etc.). Unfortunately, I can't help "to do" more about the (sometimes) brokenness of English. 😂

    English isn't broken, even if I am not personally happy with the way others use it, rather native speakers speak their own language natively and the point was brought home to me that I had to accept the reality that I sometimes had different difficulties with my own native language in relation to foreign languages.

    However, on my way out to Japan, I would not have expected that I would have had more misunderstandings with English-speakers than with Japanese speakers. Of course, it is obvious now, that with speakers of US English, I took for granted cultural assumptions that were sometimes wrong while with speakers of Japanese, I was doing everything in my power to see things from their perspective. Had I treated the Americans as I did the Japanese, there would have been fewer misunderstandings.

  • I've been using Snowflake lately, and while the SQL is similar to what I'm used to, the lack of a find/replace option in the worksheets and the absence of my favorite SSMS add-in for IntelliSense and code formatting make coding much slower. spelling bee answers

    • This reply was modified 3 months, 3 weeks ago by  sophia17.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply