Interactive Demo
Step 1 of 5
1
Explore Main Branch
See the travel preferences stored in TiDB. Try searching.
2
Fork an Experiment
Create a branch to test changes without affecting main.
3
Add Conflicting Data
Add a memory that contradicts existing preferences.
4
See the Difference
Search again - notice the conflicting result.
5
Roll Back to Main
Switch to main - conflict is gone. Time travel!
TL;DR: TiDB stores vectors + text + JSON in one table. Branching is just a WHERE clause. No Pinecone + Postgres + Redis stack needed.