I accidentally revealed the solution after running the .schema command (the solution is in the trigger code on that table). ️ Might be a record though - I got the answer in only a few seconds.
Looks like that's blocked now.
SQL Murder Mystery
31–40 of 82 posts
Re: SQL Murder Mystery
#32This 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.
Thanks!
Re: SQL Murder Mystery
#33A few years ago I ported IBM's SqlDetective from informix to postgresql and mysql. https://github.com/verpeteren/SqlDetective
Re: SQL Murder Mystery
#34I accidentally revealed the solution after running the .schema command (the solution is in the trigger code on that table). ️ Might be a record though - I got the answer in only a few seconds.
Looks like that's blocked now.
Not really: `select sql from sqlite_master` still reveals the solution.
Re: SQL Murder Mystery
#35From 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."
Whaaat, I wasn't supposed to muck around the DB for 5 minutes trying to find the starting point?
Re: SQL Murder Mystery
#36I always wanted do invest my 20 hrs into SQL.
I've already put 10 with a data analyst course so i know what a sqlite , select and joins are. I've created a not trivial query once. Is this OK for learn some more ?
Re: SQL Murder Mystery
#37I always wanted do invest my 20 hrs into SQL. I've already put 10 with a data analyst course so i know what a sqlite , select and joins are. I've created a not trivial query once. Is this OK for learn some more ?
Sure thing. I think learning SQL is never wasted time.
Try looking into SQL functions & TRIGGERs, LATERAL JOINs, ROLLUP & CUBE.
If you have even more time, check out the different things an SQL server can do when you DROP a row that contains references, how you define CONSTRAINTs, and some particular features that only some subset of SQL dialects have, such as LISTEN/NOTIFY for PostgreSQL.
Re: SQL Murder Mystery
#38Re: SQL Murder Mystery
#39OMG 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..."
well for me not looking at the schema made it more fun and I guess the plot was also pretty involving ^^
Re: SQL Murder Mystery
#40I always wanted do invest my 20 hrs into SQL. I've already put 10 with a data analyst course so i know what a sqlite , select and joins are. I've created a not trivial query once. Is this OK for learn some more ?
Sure thing. I think learning SQL is never wasted time. Try looking into SQL functions & TRIGGERs, LATERAL JOINs, ROLLUP & CUBE. If you have even more time, check out the different things an SQL server can do when you DROP a row that contains references, how you define CONSTRAINTs, and some particular features that only some subset of SQL dialects have, such as LISTEN/NOTIFY for PostgreSQL.
And, for anyone looking to pick up the basics: These ancient websites got me up to speed ages ago:
www.sqlcourse.com
www.sqlcourse2.com