You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2018. It is now read-only.
Currently we didn't have sentAt column because the timestamps were encoded in the message IDs and they are more accurate. To make it more simpler for database to process our selects with timestamps we'll need sentAt column that stores the parsed timestamp from the ID. This will use more storage, but seems logical change when we introduce advanced archiving based on queries.
To make such column we'll need a migration.
The text was updated successfully, but these errors were encountered:
Currently we didn't have
sentAt
column because the timestamps were encoded in the message IDs and they are more accurate. To make it more simpler for database to process our selects with timestamps we'll needsentAt
column that stores the parsed timestamp from the ID. This will use more storage, but seems logical change when we introduce advanced archiving based on queries.To make such column we'll need a migration.
The text was updated successfully, but these errors were encountered: