Support for virtual table (FTS5)

[0x192]

Hello,

Thanks for this amazing project!

I'm trying to use Full Text Search (FTS5) with Trailbase but without success.

It uses a virtual table which cannot be defined as "STRICT" because it is not a data table.

{
  name: "hosts_fts"
  table_name: "hosts_fts"
  acl_world: [READ]
}

CREATE VIRTUAL TABLE hosts_fts USING fts5(
    hostname,
    os_name,
    os_version,
    content='hosts',
    content_rowid='id'
);

In my case hosts_fts uses the fields in the hosts table which is defined as STRICT.

[2026-05-25T12:35:22.531895Z WARN  trailbase_schema::sqlite] PK table constraint not implemented. Use column constraints.
Error: Config(Invalid("TABLE \"hosts_fts\" referenced by API 'hosts_fts': Must be STRICT for strong end-to-end type-safety."))

[ignatz]

Hi, welcome and thanks for the issue. The error message correctly reflects the concern about type safety. I'll have a look if there's something we could do, e.g. explicitly allow certain modules. Instead short term, your best bed is probably to put in a WASM layer