
Drizzle ORM
11.4K posts

Drizzle ORM
@DrizzleORM
Sequel Statement Builder
Ukraine Katılım Eylül 2022
5 Takip Edilen52.1K Takipçiler
Sabitlenmiş Tweet

When agents met Drizzle
drizzle-orm@1.0.0-rc.4 is out 🚀
▪︎ Effect nerds, you now have native support for MySQL and SQLite drivers
▪︎ LLM agents can now use drizzle-kit CLI and SDK to manage your schema and migrations
▪︎ drizzke-kit now has MCP server and skills
▪︎ new github action to manage multi-branch migrations in teams or concurrent agent development
▪︎ next release is a v1 👀
🧵
English

It's friday so took the time to sponsor some of the OSS dependencies we rely on @trylatitude
We are now proud sponsors of @honojs @biomejs @pnpmjs @DrizzleORM @vitest_dev Knipjs
English

Sharing AutoAdmin, something we built to spin up internal tools and CRUD interfaces in minutes.
Just write your Drizzle schema and AutoAdmin generates the admin panel from it. Configure custom field types like files, images, and rich text.
Runs as a Nuxt layer. Works with SQLite (including D1, libSQL) and Postgres on Node and Cloudflare Workers.
github.com/awecode/autoad…
English


@samlambert Could you ask the @DrizzleORM team for a 1.0 skill please Mr CEO
English

Thank you to the 100+ people that added me to their PlanetScale orgs. I used the access to analyze common issues and built github.com/planetscale/sk…
These skills will fully analyze your use of PlanetScale and help you implement best practices.
English

Мігранув @DrizzleORM з v0 та v1 rc4. політ нормальний (ніби)
github.com/besidka/besidk…
Українська

In the next version of Turborepo...
Nub support! github.com/vercel/turbore…
English

Incase people dont know how to create self-referential tables in @DrizzleORM , this is how you do it
The rows with parent_group_id NULL are the root groups, while the rest are child groups. This works for infinite depth/nesting (although i cant think why you'd need it)

English

Only supporting zero, one, or unlimited
I think it was a @swyx tweet that put me onto it, but building in support for 2 of a thing inevitably leads to later needing 3
So the moment you need more than 1, make it unlimited
Dominik Ferber@dferber90
what’s an „overengineered“ dev practice that ended up saving you later? this was the top answer by a wide margin
English

When agents met Drizzle
drizzle-orm@1.0.0-rc.4 is out 🚀
▪︎ Effect nerds, you now have native support for MySQL and SQLite drivers
▪︎ LLM agents can now use drizzle-kit CLI and SDK to manage your schema and migrations
▪︎ drizzke-kit now has MCP server and skills
▪︎ new github action to manage multi-branch migrations in teams or concurrent agent development
▪︎ next release is a v1 👀
🧵
English

@DrizzleORM @andrii_sherman I hope there’s expo sqlite in the next release
English

@Timur_Yessenov it's a matter of control you have to have to guardrail llms while being able to iterate on schema with destructive migrations too
English

@DrizzleORM That’s the part I’m curious about. Is the remaining work mostly deterministic diffs, branch merge semantics, or the CI review UX around generated migrations?
English

@atiya_ag Here
Drizzle ORM@DrizzleORM
Drizzle for Platforms It's a set of APIs we are building for modern LLM platforms to solve their SQL problems if you're an agentic platform - we would love to chat 👀 drizzle-kit now fully supports non-tty environments, has MCP server, versioned skills and deterministic migrations generation
English

@DrizzleORM Whoa, nice. Right now I have to straitjacket my agent to get it to do drizzle migrations correctly. When and where will the skill and MCP be available?
English

@Timur_Yessenov Yes, there are couple of things left and we are there
English

@DrizzleORM The MCP server is interesting, but the GitHub Action for multi-branch migrations is the part I’d watch. Schema changes are where agents collide. If Drizzle can make the migration diff deterministic across concurrent agent work, that’s a real dev workflow unlock.
English

















