Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    I'm not sure what you're asking here. The role of a UserID in a time series would be the same as its role in any other table: identifying the user. The article you linked doesn't even mention user id's. The word "attribute" is apparently being used in the article to mean either "data points" or "anything that is not part of the primary key." Commented May 23, 2018 at 16:15
  • @RobertHarvey I've edited my question to clarify a bit more, not sure if it'll help. Commented May 23, 2018 at 17:10
  • 3
    OK, well you would add a column for userid. What do you put in there? The userid corresponding to the user for which a particular data record pertains. I think your confusion stems from the idea that user id's will somehow be unique in this table, or that the database will be generating them. Neither of those things is true. Commented May 23, 2018 at 19:29