Vectors + Metal is an insane combo. We made vector storage and search into MySQL meaning PlanetScale is the first RDBMS to allow vector search as part of a full SQL query. You can pre and post filter while doing vector lookups reducing 3-4 queries into 1
Find these and all other Directus Labs extensions here: github.com/directus-la... 👉 YouTube Embed Interface
Search and embed YouTube videos directly within your collections. Need to use the embed elsewhere? Simply copy the code from the drawer. No more tab-switching or format-guessing.
youtu.be/3X4nHqRL5rE 👉 Field Comments Module
Leave comments on specific fields to provide context, requirements, or feedback. A subtle icon shows which fields accept comments, with badges indicating when comments exist.
youtu.be/hZsMbNNgr74 👉 Inline Repeater Interface
Manage repeatable form fields with intuitive inline editing and drag-and-drop reordering. Perfect for product features, team members, or any structured repeating content.
youtu.be/bmukVPKoq0s We just released 3 new extensions to supercharge your content and data workflows 🧵 
Get started today by enabling vector support on your database branch in the PlanetScale dashboard.
Vectors especially shines when running on Metal. Using vector indexes on PlanetScale Metal ensures that loading vector partitions from InnoDB to answer queries will be as fast as possible.
pscale.link/metal Only the tree and a small, fixed number of relevant partitions need to be in memory when building and querying the index, allowing efficient operation with vector data up to 6x bigger than available memory.
SPANN is a hybrid index design that combines the best aspects of partition-based and tree-based indexes. In SPANN, vectors are assigned to small partitions, which are stored in hidden InnoDB tables.
One of the biggest differentiators of PlanetScale vector support is the ability to use indexes larger than RAM. We are the first to incorporate an index based on SPANN (Space-Partitioned Approximate Nearest Neighbors) into an RDBMS.
Writes and queries work like a normal RDBMS. Store your vector data in a column in your existing database, build an index with an ALTER or CREATE VECTOR INDEX statement, or write SELECT statements with JOIN and WHERE clauses like any other data.
PlanetScale vectors is now GA!
We have made vectors a first-class part of MySQL - focusing on robustness to make sure vector support is as solid as every other data type MySQL supports.
pscale.link/vectors 
very good
Another day, another concurrency issue.
Had a lovely time chatting with Paul about when to use existing sync engines vs when to roll your own. Would love your feedback on the episode!
Very happy with my work / vibe balance!
👏
We actually have a third structure, which is virtual branches - you can work on multiple branches (or stacks of branches) at the same time in one working directory. In case multiple stacks or branches have no interdependencies.
I like the two levels. Per-commit review within a branch means they are all merged together. Stacking branches means the bottom should be merged first, but stacks above it depend on those but don’t need to be merged at the same time. Its a useful mental difference when working on them.
Prefer real human connection when you need support?
Join our Discord and chat live with fellow Prisma users, get expert help from our support team, and ask our engineering team your burning questions during regular AMAs.
Let’s build together! 🤝
pris.ly/discord 
There's never been a better time for mobile CI, and we're committed to shaping this future. We believe more innovation is essential.
Read our full blog post on the topic:
thedevsdividend.substack.com/p/mobile-ci... The web ecosystem has had this capability for years. Even browsers can run code natively compiled with a Wasm compiler. Meanwhile, in the mobile space, all we can do is write a pipeline and ask a mobile CI provider to run it.