Dockery/Trilium
1
0
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2026-02-06 06:29:19 +01:00
Code Issues Packages Projects Releases Activity

chore(monorepo): put back docs

Browse Source
This commit is contained in:
Elian Doran
2025-04-18 16:10:44 +03:00
parent 0143db5b45
commit ca37a416bb
879 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/Developer Guide/Developer Guide/Development and architecture/Synchronisation/Content hashing.md Normal file
View File

@@ -0,0 +1,17 @@
# Content hashing
Entity hashing is done in `content_hash#getEntityHashes`.
* It works by looking at the `entity_changes` table and going through each of the entity names/types:
* `blobs`
* `attributes`
* `revisions`
* `attachments`
* `notes`
* `branches`
* `etapi_tokens`
* `options`
* For some reason `note_reordering` entities are ignored specifically.
* All the rows in `entity_changes` are then ordered alphabetically, based on their `entityId`.
* Every entity row is then grouped by `entityName` and then by sector. The sector is defined as the first character of the `id`.
* The hash is altered to add the `isErased` value as well since the hash of deleted entries is not updated.
* For each sector, the hash is calculated using `utils.hash`, using SHA1 encoded as Base64.