Skip to main content

Storing unix timecode in number question

  • March 25, 2021
  • 0 replies
  • 3 views

Hello.

I built a small chat bot that fetches some data on regular basis (weekly) and stores the results in database.
So I run a job daily that does this work, and to determine which records I need to check I added previousCheck field with type number, where I store unix timecode after every check (so the next time I get to it will be in a week).

Is this a bad idea? Will I run into problems in 10-15 years?
How long is Airtable’s integer?

This topic has been closed for replies.