To be fair. That Golang implementation looks overly verbose. I mean compare the Typescript and Golang implementation. The Golang one isn't even readable. I'd personally use something else instead.
Prisma – Database tools for modern application development
31–40 of 88 posts
Re: Prisma – Database tools for modern application development
#32What is Prisma actually? Is it an ORM or a client for a db that exposes a GraphQL API for the data stored?
Re: Prisma – Database tools for modern application development
#33Looks like the traditional caveats for ORMs would apply here. Many painful lessons have been learned in that field.
What would be interesting to see is the cost of change i.e. how de-coupled things are to make changes simple.
Changes like: Adding a field To changing a relationship between entities and such.
Re: Prisma – Database tools for modern application development
#34Looks like the traditional caveats for ORMs would apply here. Many painful lessons have been learned in that field. What would be interesting to see is the cost of change i.e. how de-coupled things are to make changes simple. Changes like: Adding a field To changing a relationship between entities and such.
That's a good question. As long as you have additive changes, Prisma can do the change automatically for you. As soon as it's a change where anything will be dropped (field, relationship etc), Prisma will prompt you and ask if you want to perform that breaking change. The only command you need to know for data model changes is `prisma deploy`.
Disclaimer: I work at Prisma.
Re: Prisma – Database tools for modern application development
#35Back when prisma was emerging out of graphcool, every google documentation search sent me to graphcool, every graphcool page was full of broken links, and the shiny new prisma docs were unusable (including unviewable on my iPad that I use for researching tech I might use while sitting on the couch). It painted such a clear picture of a company that absolutely does not get the importance of API documentation to the su…
Thanks for your upright feedback! You must have caught us in a bad moment, in the transition one year ago from Graphcool to Prisma we indeed needed to do a lot of work in the docs.
Nowadays the Google experience should be much better, while our docs actually represent the product.
Would be great if you can give it another try, as I'm convinced that the docs improved significantly over the last year. Disclaimer: I work at Prisma.
Re: Prisma – Database tools for modern application development
#36What is Prisma actually? Is it an ORM or a client for a db that exposes a GraphQL API for the data stored?
That's a good question.
The main focus of Prisma is the ORM part and not the GraphQL API anymore. We're still using GraphQL to communicate between Query Engine and the backend client in the languages we support like TypeScript or Go, but when communicating with backend to database, GraphQL is not that relevant anymore and rather a separate concern how you want to expose your API later.
When accessing the database from your backend, type-safety is becoming more and more important. Instead of writing a GraphQL string in your code, with the Prisma Client you get a type-safe programmatic API to access your data. You can imagine it as your own SDK. The difference to many ORMs is, that we generate a custom Client for you, which is way more powerful.
Disclaimer: I work at Prisma.
Re: Prisma – Database tools for modern application development
#37Forgive me the obvious elephant in the room - where is Swift and Java/Kotlin support?
For Kotlin/Java you can probably use jOOQ (https://www.jooq.org/)
Re: Prisma – Database tools for modern application development
#38I’ve tried Prisma over the last few months, but eventually decided against adopting it in our product because it seems very inflexible when working with many-to-many relationships. In particular, filtering on foreign keys doesn’t seem possible and requires SQL table joins, which (in our case) has an immensely negative performance impact. Also, the query chaining API doesn’t lend itself well to filtering on multiple r…
Forgive me if I’m missing something here, but joins seem pretty much the only way to do performant foreign key filtering to me.
Is this not what you were talking about?
Re: Prisma – Database tools for modern application development
#39I will never understand the desire to add ever more layers to well understood patterns and services. I fail to see the value add of prisma over any decent database.
It’s not a database.
SQL isn’t typed. And writing migrations and client libraries is otherwise painful. That’s basically the value add.
Re: Prisma – Database tools for modern application development
#40I will never understand the desire to add ever more layers to well understood patterns and services. I fail to see the value add of prisma over any decent database.
It’s not a database. SQL isn’t typed. And writing migrations and client libraries is otherwise painful. That’s basically the value add.
Sql is not only typed, its very strongly typed. Please dont confuse the lack of explicit annotations in typical sql for a lack of types. Sql is the prototypical killer app for type inference. Its so good, most people think it's untyped