Prisma
@prisma.io
4 months ago Let's say we want to form a totally different query than we'd get from Prisma ORM.
Perhaps using `WITH users AS` so we can shape a different output.
💬 1
♻️ 0
❤️ 0
Let's say we want to form a totally different query than we'd get from Prisma ORM.
Perhaps using `WITH users AS` so we can shape a different output.
Next, create a new directory inside your existing `prisma` directory called `sql`.
In here, place a .sql file such as `getUsers.sql`.
✅ Start by enabling `typedSql` as a preview feature in your schema
Using a type-safe ORM means easier query authoring, fewer bugs, and better coordination across teams.
Prisma ORM also allows you to drop down to raw SQL in a type-safe way as well. You're never restricted to just using the ORM.
Here's a quick look at how to use it 👇
Right? In the end, we're happy to step into things that Apple could have solved, but some of these feel like such a no-brainer. They might solve this at a more foundation level in the future, but who knows how long that will take.
Momentum is essential for developers to match the pace of business, and it's also key to fueling creativity and crafting superior applications. In this post, we explore factors that disrupt momentum and offer strategies to address these hurdles.
#Swift
tuist.dev/blog/2025/0...
It has been a few weeks since we launched Prisma Postgres in GA and shipped a brand new website. 🎉
Have you found the easter egg yet 👀
Another week, another super fun Git nerd article. Today I posted about doing interdiff review with the git range-diff command.
blog.gitbutler.com/interdiff-re...
Denver folks — join us for a Geospatial Happy Hour on Wednesday, March 12th at 7 PM MST. Come enjoy drinks, tacos, discussing geospatial data, and meeting the Earthmover team. Register: lu.ma/o6r39p6j
seo dorks, is this good, i don't think it's good
Is that what you're thinking more or less? How would you wanna write this, with a state machine, a DAG or just in code with a kind of "router" function? Also, are you looking for functions that kind of run forever or something that is mostly executing to completion?
This is interesting, we have modeled ideas like this, especially for AI use case where each step.run within an Inngest function returns the current state of the entire workflow (like a DO) then the loop takes that current state and decides what to run next, returning the state.
Big milestone this week:
100,000 developers are using the Prisma Data Platform to take the pain out of working with databases 🎉
Thank you to everyone who is already part of our journey! 🙌
If you want to join in, check out how to get started with Prisma Postgres 👉 pris.ly/ppg-getting...
We've done pretty well but want to do better and there's so much more to do. If you or someone you love is an excellent dev rel who can drive engagement, tell good stories, and can work in London or wants to relocate, I'd love to chat.
Every developer at tldraw also works with the community, writes docs, makes tweets, and presents about the project. The company started as a fun public flex and kinda stayed stay way.
We are hiring a Developer Relations role in London 🧑💻
Apply here:
tldraw.dev/jobs?ashby_j...
source code here
gist.github.com/mootari/724d...
arrow % by @mootari.social
now using a combination of octo, diffview, and lazygit for my git workflow. it's pretty decent. might replace lazygit with neogit soon.
Very cool and exactly what I had in mind re "binding to custom software". Curious whether you've also managed to create bindings for existing software e.g. Figma / VSC controls based on your workflows.
Loading spinners are papercuts (at minimum)
Something like that! This is what we have atm, kinda like a Jupyter notebook but with embedded terminals
bsky.app/profile/elli...
Definitely working hard to make it easy to go from shell history -> documentation/runbook -> executable workflow
TIL: Buck has documentation for the underlying pbxproj types, such as "PBXBuildFile". Somebody had to do it when Apple won't 😅
buck.build/javadoc/com/...
This is happening today. Five hours from now. See you there!