BigQuery Web: Rename min_tstamp in sessions_userid_manifest_this_run

[bill-warner]

Inconsistent naming of the tstamp between sessions_userid_manifest_staged and sessions_userid_manifest_this_run.

Suggest we change min_tstamp to start_tstamp here to align with other web models.

[colmsnowplow]

It's min_tstamp in Redshift too

data-models/web/v1/redshift/sql-runner/sql/standard/03-sessions/01-main/05-sessions-prep-manifest.sql

Line 27 in e1e10fb

MIN(start_tstamp) AS min_tstamp

I'm on board with changing the name to whatever. I think I went with min_tstamp as it represents the first timestamp found for a given domain_userid, rather than the start of a session/page view. In my head, the thought process was that if we want it to be called start_tstamp, it should be first_start_tstamp.

Having said that, it's all entirely academic, so whatever we wanna name it I won't argue - I agree that it should have the same name across all 3 though. :)

[bill-warner]

All fair points. I think given a) we use start_tstamp within the users module to denote the first time a user is active and b) the sessions_userid_manifest_staged table, which we insert the data into, uses start_tstamp across all 3 models already it makes most sense to rename to start_tstamp

[colmsnowplow]

Fair, I'm on board.