Skip to content

Commit

Permalink
Update documentation for database fields in GenesisFlake
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
kievitsp committed May 23, 2024
1 parent 3474e1a commit 7b4377b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/02_database/01_fields-tables-views/04_timestamps.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 7b4377b

Please sign in to comment.