Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SQL Murder Mystery

mystery.knightlab.com

Post reply on HN
Print view View original

21–30 of 82 posts

Re: SQL Murder Mystery

#22

Post by dang »

rrix2 wrote: post #16

This version doesn't support INSERTing the solution from the web. https://mystery.knightlab.com does, though, and provides some guidance out the door. Fun little thing, thanks!

Ok, we'll change the URL to that from https://sql-murder-mystery.datasette.io/sql-murder-mystery, since it seems to be the original source also.

Re: SQL Murder Mystery

#23

Post by irjustin »

OMG I love this. I just sent it to my buddy who as a PM is learning SQL to not rely on the BI team since the turnaround can be days.

Ultra tiny desire - I only wish there was more on the story line/intro framing. Took at look at the schema and was like "What is Get fit now? - ohhhh, it's a gym... got it..."

Re: SQL Murder Mystery

#25

Post by kroltan »

pbiggar wrote: post #18

Be warned that there are spoilers built into the DB, if you look too closely. The trigger on the solution DB has the answer built into the SQL, as I learned when I ruined the game for myself.

To be fair, a hex of the answer, so you only spoil yourself if you're very good at reading base-16-encoded ASCII data.

Re: SQL Murder Mystery

#26

Post by jandrese »

dlgeek wrote: post #11

From the better link from kevindong: "A crime has taken place and the detective needs your help. The detective gave you the crime scene report, but you somehow lost it. You vaguely remember that the crime was a murder that occurred sometime on Jan.15, 2018 and that it took place in SQL City . Start by retrieving the corresponding crime scene report from the police department’s database."

Heh, I was looking at all of the murders in the police report database trying to figure out which one it was talking about.

Re: SQL Murder Mystery

#28

Post by pbiggar »

kroltan wrote: post #25
pbiggar wrote: post #18

Be warned that there are spoilers built into the DB, if you look too closely. The trigger on the solution DB has the answer built into the SQL, as I learned when I ruined the game for myself.

To be fair, a hex of the answer, so you only spoil yourself if you're very good at reading base-16-encoded ASCII data.

I saw an unhexed answer in the original datasette link.

Re: SQL Murder Mystery

#29

Post by LifeIsBio »

> Time to break out the champagne!

This was a lot of fun; I'd definitely play level 2.

The nice thing about it was that you had some flexibility around getting the exact SQL query, and just visualizing a slightly larger superset of the data.

Post reply on HN