Live data from Hacker News

Viewing profile — MarkusWinand

MarkusWinand

HN member
Joined
Fri, Jan 17, 2014, 11:27 AM UTC
HN karma
1,995
Public activity
166 items

About MarkusWinand

Autor, Trainer, Coach.

All about SQL:

https://winand.at/ https://use-the-index-luke.com/ https://modern-sql.com/

Recent public activity

  1. story
  2. comment
    Comment #46703910

    INSERT ... ON CONFLICT has fewer surprises in context of concurrency: https://modern-sql.com/caniuse/merge#illogical-errors Besides portability, there is IMHO nothing against INSER…

  3. story
  4. story
  5. story
  6. story
  7. story
  8. story
  9. story
  10. comment
    Comment #38533276

    > Making a pretty diagram where all the behaviours from various DBMSs are listed is left as an exercise to the author. :) It's there already! It's in the chart as footnote "b": Out…

  11. comment
    Comment #38532256

    No question, such a query should not be written. That's probably the reason why this odd behavior, which is even different in various DBMSes, is not causing everyday problems.

  12. comment
    Comment #37850367

    > SQLite also ignores size restrictions on text columns; [...] requires a trigger. I'd go for CHECK constraints first: https://www.sqlite.org/lang_createtable.html#ckconst > Proced…

  13. comment
    Comment #37849614

    The existing implementations (Oracle DB, SQL Server, MariaDB, Big Query) come with their problems too. I was a big fan of the new features when it came out in 2011, but pratically …

  14. comment
    Comment #37848934

    Fair point, looks suspicious on first sight. I've checked my tests briefly: It's accepted as table and column name. As mentioned in footnote [0] I haven't checked different context…

  15. comment
    Comment #37848173

    Author of the website here. All charts on modern-sql.com are backed by tests. I also keep them up-to-date by running them for new releases when they appear.

  16. comment
    Comment #37848133

    I wonder why you are so focused on SQL:2011? Since then there was SQL:2016 and now there is SQL:2023. Also, which features in particular are you missing in PostgreSQL? Merge was ad…

  17. comment
    Comment #37655107

    > The standard is not generally available. Most of us will never learn what is in it. It also not aimed at users, but at implementors. Funny enough, they don't read the standard ei…

  18. comment
    Comment #37647935

    I recently covered MERGE on modern-sql.com: https://modern-sql.com/caniuse/merge There I also look at limitations of some implementations and problems such as not reporting ambiguo…

  19. comment
    Comment #36156728

    The rationale behind the width is more the ease of reading than anything else: https://en.wikipedia.org/wiki/Line_length But thanks for the feedback. There is a rework pending anyw…

  20. comment
    Comment #36155601

    I'm studying the SQL standard for years now and compared to other standards that I know (XSLT, a little CSS, decades ago POSIX, C and C++) the SQL standard is really hard to make s…

  21. comment
    Comment #36155533

    > It comes down to how you plan to shard data and distribute queries when data doesn't fit on a single node. A problem everbody would love to have but pretty much nobody actually h…

  22. comment
    Comment #36155210

    This is one of the questions I try to answer at https://modern-sql.com/

  23. comment
    Comment #36154918

    That particular one is already available in PostgreSQL 15. https://modern-sql.com/caniuse/unique-nulls-not-distinct

  24. comment
    Comment #36154799

    Fixed. I wonder why Google sent me to http...

  25. comment
    Comment #36154776

    Luckily pretty much nobody needs the standard documents. It's actually my aim at https://modern-sql.com/ to make the relevant information more accessible — in particular including …