-
Notifications
You must be signed in to change notification settings - Fork 263
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
time_inserted in the 'play' table... #199
Comments
After getting nflgame setup to auto-populate the nfldb database, it appears that the time_inserted is based on when the records were inserted into the database, and have no connection at all to when the play actually happened. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(not a Python guy, not a PostreSQL guy, but understand other languages and DB's - so speak slow and loud)
How is the value in the 'time_inserted' field determined? It doesn't appear to be a default value on the table or set via trigger, so I assume that it is set by whatever script populates records in that table. Is that a timestamp based on when the script performed the insert [ i.e. insert into play(time_inserted) values(now()) ], or does that come from the NFL data and is then just pushed into nfldb?
I'm trying to approximate as closely as possible when the real time start of a play occurred (i.e. UTC timestamp associated with the snap of the ball). Is there a way to come close to this with nfldb?
Thanks in advance.
The text was updated successfully, but these errors were encountered: