Merge pull request #1680 from genesiscommunitysuccess/pk/timestamp

Update documentation for database fields in GenesisFlake
genesiscommunitysuccess · May 23, 2024 · b07bb96 · b07bb96
2 parents a670859 + 56e559d
commit b07bb96
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/docs/02_database/01_fields-tables-views/04_timestamps.mdx b/docs/02_database/01_fields-tables-views/04_timestamps.mdx
@@ -9,7 +9,12 @@ tags:
   - genesisflake
 ---
 
-When you generate a database on the Genesis low-code platform, every table in the database is given a TIMESTAMP field. This contains a timestamp value that is generated automatically by GenesisFlake every time a change is made to the database. The `TIMESTAMP` field in GenesisFlake represents the creation time of a record, not the last modified time.
+When you generate a database on the Genesis platform, every table in the database is given a TIMESTAMP and a RECORD_ID field.
+
+- The `TIMESTAMP` field value is generated automatically by GenesisFlake every time a change is made to the database.
+- The `RECORD_ID` field is the `TIMESTAMP` value when the record is first created, it will never change.
+
+The database generates a new `TIMESTAMP` for every modify operation, even if no other fields are changed.
 
 To create these values, GenesisFlake generates IDs in a similar manner to Twitter’s [snowflake](https://developer.twitter.com/en/docs/basics/twitter-ids). It is able to generate these IDs without having to perform database-level synchronisation - which ensures high performance.