Issue observed in python with library libsql 0.1.11. Without the delete both rows are reliably returned by vector_top_k, it doesn't seem like an insert doing an overwrite, more like a too-broad delete ...
The fastest way to understand the full workflow (Drizzle ORM, browser-safe migrations, optional encryption, and Turso sync) is to run the demo app. Using raw SQL in Rust is verbose, and Rust ORMs ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results