Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

encourage use of get_fit tables #11

Open
fluidpixel opened this issue Nov 22, 2019 · 4 comments
Open

encourage use of get_fit tables #11

fluidpixel opened this issue Nov 22, 2019 · 4 comments

Comments

@fluidpixel
Copy link

Currently you don't need to access the get fit tables in order to find the solution.

spoiler alert...

The event that both witnesses attended only has one other person checkin on that day, which is the killer. If the event had a few (many?) more check-ins it might encourage digging into the interviews and therefore gym details...

@JoeGermuska
Copy link
Member

yes, I figured that out as I was creating an "instructor's guide." I think it'd be worth adding some noise.

@Khelavaster
Copy link

Khelavaster commented Dec 17, 2019

Same goes for the second part of the puzzle.

spoiler

If you work backwards and select people who went to see the concert three times in specified timespan, it returns two people. But only one of those people has a driver's license, which ends the search right there. Also judging from the name, the other person is a man, which also ends the search.

It would be useful to have more matches for the concert goers, so that the car and other details are relevant with this approach.

@JoeGermuska
Copy link
Member

if people want to cook up some SQL statements that help increase noise, we'd welcome that.

@Khelavaster
Copy link

Sure thing. Where do you want them checked in?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants