Tweets

You blocked @RhodiumToad

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @RhodiumToad

  1. Pinned Tweet
    17 Nov 2019

    Wow, blocked me, for pointing out the transparency problems with his social media site.

    Undo
  2. 12 Dec 2019

    And now that Christoph has found a case where the spec allows a query of unbounded length using only keywords, let's limit it to cases with no loops

    Show this thread
    Undo
  3. 12 Dec 2019

    (Note, PostgreSQL accepts a number of cases of indefinite repetition, so I'm limiting this challenge to valid SQL 2016 foundation syntax)

    Show this thread
    Undo
  4. 12 Dec 2019

    A challenge: what SQL statement contains the longest possible sequence of consecutive keywords? (My best so far has 13 consecutive keywords)

    Show this thread
    Undo
  5. 12 Dec 2019

    Today's fun fact: "Tory" comes from the Irish word for a bandit. Any relevance to modern politics is left as an exercise for the reader

    Undo
  6. 9 Dec 2019

    PSA: When asking for help, show YOUR OWN code / problem description, don't just point to a random forum post and say "I'm having the same problem as this". It makes it impossible to see what simple errors you may have made, or differences between your issue and the post

    Undo
  7. 26 Oct 2019

    Another SQL style tip: always a space before the paren in constructs like "OVER (", "FILTER (", etc. Avoid making things look like function calls when they're not.

    Undo
  8. 26 Oct 2019

    SQL style tip: treat "SELECT DISTINCT" as one keyword that happens to have a space in it. Never put a newline before DISTINCT, and never put an open paren directly after it. When using COUNT(DISTINCT ...), if you absolutely need a paren, then always have a space before it.

    Undo
  9. 25 Oct 2019

    PSA: The error message is the part that starts with "ERROR:". Any DETAIL: or HINT: that follows may be informative, but it is NOT the error message. ALWAYS READ THE ERROR MESSAGE.

    Undo
  10. 21 May 2019

    So now I'm curious: to the two people who voted to keep postfix operators in my poll: why? Do you have a use case or an example of existing usage?

    Undo
  11. 17 May 2019

    Quick poll: should remove support for postfix operators in expressions, or keep them? Their existence makes parsing a lot harder.

    Undo
  12. 1 Apr 2019

    Today's optimization tip: when dealing with queries over many tables, consider increasing from_collapse_limit and join_collapse_limit.

    Undo
  13. 14 Mar 2019

    Also it insists on labelling .h files as being C++ or Objective-C (rather than the C that they actually are) regardless of what I put in .gitattributes.

    Show this thread
    Undo
  14. 14 Mar 2019

    Github language statistics never cease to baffle me. Hundreds of lines of SQL and a 3-line .dir-locals.el, and it says the repo is 100% Emacs-Lisp.

    Show this thread
    Undo
  15. 27 Feb 2019

    I will probably regret signing up for this thing.

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·