Can we have a Hanzo badger?


  • SockDev

    Continuing the discussion from What coulor is this dress?:

    @anonymous234 said:

    [CURSES, HANZO'D AGAIN!]

    I seem to do this weirdly often :laughing:

    But, yeah, why not have a Hanzo badge?

    <!-- Emoji'd by MobileEmoji 0.2.0-->


  • We have INB4 fail, which is close.



  • Hanzo would happen too much, awarding the badgers would eat into @PJH's pub time seeing as @boomzilla would be too busy not doing his job to award them.


  • SockDev

    But that's an automated badger though? I'm not sure the Hanzo badger could be automated like that.

    <!-- Emoji'd by MobileEmoji 0.2.0-->


  • All of the INB4 badgers are manual IIRC.



  • @loopback0 said:

    All of the INB4 badgers are manual IIRC.

    I really need to sort that out and at least get the INB4 .*ate ones automated...


  • BINNED

    @loopback0 said:

    Hanzo would happen too much, awarding the badgers would eat into @PJH's pub time seeing as @boomzilla would be too busy not doing his job to award them.

    Sorry, I just had to quote this to nominate it for the highest density of WTDWTF memes in a single sentence, ever.


    Filed under: Cue attempts to beat it by using unreasonably long run-on sentences



  • If only I'd added a Filed under: to it :laughing:


  • SockDev

    Needs several @accalia­s and a @blakeyrant too ;)

    <!-- Emoji'd by MobileEmoji 0.2.0-->


  • @PJH said:

    I really need to sort that out and at least get the INB4 .*ate ones automated...

    Ewww...

    WITH auto_closed_topics AS ( /* this clause will change */
        SELECT 1923 topic_id 
        UNION ALL
        SELECT 2825 topic_id
    ),
    closing_post AS (
        SELECT MAX(post_number), id post_id, topic_id, created_at
            FROM posts p
            WHERE topic_id IN (
                SELECT topic_id FROM auto_closed_topics
            ) AND
            post_type=2 AND
            raw ILIKE 'This topic was automatically closed after %'
            GROUP BY id, topic_id, created_at
    ),
    nate_posts AS (
        SELECT p.user_id, p.post_number, p.id post_id, p.topic_id, p.created_at, p.raw, row_number() OVER (PARTITION BY p.topic_id ORDER BY p.created_at DESC) as rank
        FROM posts p
        JOIN closing_post cp ON p.topic_id=cp.topic_id
            AND p.created_at > cp.created_at - INTERVAL '1 minute'
            AND p.id != cp.post_id
    )
    SELECT user_id, post_id, created_at granted_at  FROM nate_posts WHERE rank=1
    

  • SockDev

    @PJH said:

    Ewww...

    …better than having to do it manually, at least ;)

    <!-- Emoji'd by MobileEmoji 0.2.0-->

  • BINNED

    @PJH said:

    post_type=2 AND
    raw ILIKE 'This topic was automatically closed after %'

    And this is where that damned post_type parameter would make sense as an integer if it were to use more values than just 1 and 2...


  • BINNED

    Actually, hold on... There's topics.auto_close_at. Doesn't seem to have an index on it, but I don't see one on raw either, might still be a bit more efficient and/or reliable?



  • @RaceProUK said:

    …better than having to do it manually, at least

    Meh. It's done - and the 3 relevant INB4 badge pages now link to the posts concerned now.



  • Oh - and discovered another discobug in the process:



  • This topic was automatically closed after 14 days. New replies are no longer allowed.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.