From 7b4377b877411c3a3051e42f828c109318d778c0 Mon Sep 17 00:00:00 2001 From: kievitsp Date: Thu, 23 May 2024 10:23:48 +0100 Subject: [PATCH] Update documentation for database fields in GenesisFlake The documentation for GenesisFlake database fields has been updated. The updated documentation includes the addition of a `RECORD_ID` field alongside the existing `TIMESTAMP` field in the database. It also provides further details on how and when these fields are updated. --- docs/02_database/01_fields-tables-views/04_timestamps.mdx | 2 +- 1 file changed, 1 insertion(+), 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 index c97a6d3d0f..d68a6422b5 100644 --- a/docs/02_database/01_fields-tables-views/04_timestamps.mdx +++ b/docs/02_database/01_fields-tables-views/04_timestamps.mdx @@ -12,7 +12,7 @@ tags: When you generate a database on the Genesis low-code 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 was first created, it will never change. +The `RECORD_ID` field is the `TIMESTAMP` value when the record is first created, it will never change. The database will generate 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.