Files
Meshtastic-Android/core/database
James Rich 0e59ed7a13 feat: add FTS5 full-text message search
Leverage Room 3.0.0-alpha04's FTS5 support to enable searching
message history. Uses external content table backed by Packet entity.

Schema changes (migration 38→39):
- Add message_text column to Packet entity
- Create PacketFts virtual table with FTS5 index on message_text
- Content triggers auto-sync FTS index on INSERT/UPDATE/DELETE

Search stack:
- PacketDao: searchMessages/searchMessagesInConversation queries
- DatabaseManager: backfillSearchIndexIfNeeded on DB switch
- PacketRepository: searchMessages with FTS query sanitization
- MessageViewModel: debounced search (300ms, min 2 chars)
- MessageSearchBar: M3 TopAppBar replacement pattern

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-05-06 13:52:50 -05:00
..

:core:database

This module provides the local Room database persistence layer for the application using Room Kotlin Multiplatform (KMP).

Key Components

  • MeshtasticDatabase: The main Room database class, defined in commonMain.
  • DAOs (Data Access Objects):
    • NodeInfoDao: Manages storage and retrieval of node information (NodeEntity). Contains critical logic for handling Public Key Conflict (PKC) resolution and preventing identity wiping attacks.
    • PacketDao: Handles storage of mesh packets, including text messages, waypoints, and reactions.
  • Entities:
    • NodeEntity: Represents a node on the mesh.
    • Packet: Represents a stored packet.
    • ReactionEntity: Represents emoji reactions to packets.

Security Considerations

Public Key Conflict (PKC) Handling

The NodeInfoDao implements specific logic to protect against impersonation and "wipe" attacks:

  • Wipe Protection: Receiving an is_licensed=true packet (which normally clears the public key for compliance) will not clear an existing valid public key if one is already known. This prevents attackers from sending fake licensed packets to wipe keys from the DB.
  • Conflict Detection: If a new key arrives for an existing node ID that conflicts with a known valid key, the key is set to ERROR_BYTE_STRING to flag the potential impersonation.

Module dependency graph

graph TB
  :core:database[database]:::kmp-library

classDef android-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-application-compose fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef compose-desktop-application fill:#CAFFBF,stroke:#000,stroke-width:2px,color:#000;
classDef android-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef android-library fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-library-compose fill:#9BF6FF,stroke:#000,stroke-width:2px,color:#000;
classDef android-test fill:#A0C4FF,stroke:#000,stroke-width:2px,color:#000;
classDef jvm-library fill:#BDB2FF,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-feature fill:#FFD6A5,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library-compose fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef kmp-library fill:#FFC1CC,stroke:#000,stroke-width:2px,color:#000;
classDef unknown fill:#FFADAD,stroke:#000,stroke-width:2px,color:#000;