• @[email protected]
    link
    fedilink
    22
    edit-2
    5 months ago

    Stage 5 can give you a huge boost in writing complex queries!

    You say that like it’s a good thing. I like my queries simple.

    Also - the stuff you have under “stage 6” should all be learned before “stage 2” in my opinion. Knowing how to write efficient queries is far more important than group by / join / etc.

    • fmstrat
      link
      fedilink
      English
      135 months ago

      Huh? How do you write an efficient query and not take into account joins? A single table query? Are you a Prisma fan?

    • @Lmaydev
      link
      3
      edit-2
      4 months ago

      Joining is one of the simplest and most useful things in SQL.

      How can you possibly query without it?

      Simple queries are obviously better but not everything can be achieved with simple selects.

  • @[email protected]
    link
    fedilink
    155 months ago

    I imagine it depends on use case. Anything more advanced that subqueries/CTEs is largely the domain of ETL developers (not exclusively, obviously) but most others using SQL don’t need anything that advanced.

  • @[email protected]
    link
    fedilink
    English
    125 months ago

    CTEs enhance readability, documentation, and testing imo. I’m very pro CTE whenever a subquery isn’t the obvious choice.

  • @[email protected]
    link
    fedilink
    95 months ago

    It’s always bothered me when I write subqueries that have to be run on each row. Good to know that there’s a better way.

  • @Lmaydev
    link
    24 months ago

    CTEs are amazing. I discovered them semi recently and it’s such a great tool to have in your belt.

    Partitioning is definitely something I need to work on.

    • mac
      link
      125 months ago

      • @Lmaydev
        link
        24 months ago

        Lol

        But just that popup existing is irritating.