nikolasburk

11 ms·

1. 61.▲
   by nikolasburk 6y ago

   Thanks so much for sharing your experiences with Prisma! > The main problems I've run into have been around utilizing standard postgres naming patterns (snake case for tables and fields instead of camelcase) and mapping the names in
2. 62.▲
   by nikolasburk 6y ago

   Scarily close to reality :D
3. 63.▲
   by nikolasburk 6y ago

   I think one very common characteristic of most ORMs is that tables are defined in terms of classes (often called models ). You then instantiate these classes to work with the model instances for data storage and retrieval. Prisma takes
4. 64.▲
   by nikolasburk 6y ago

   Thanks a lot for the clarification, Tirumarai! (Remote JOINs look awesome btw, congrats on the release :)
5. 65.▲
   by nikolasburk 6y ago

   Today's release unfortunately doesn't include our migration solution Prisma Migrate [1] yet. We totally understand that a lot of people want to get "database access" and "schema migrations" with the same tool&#
6. 66.▲
   by nikolasburk 6y ago

   Prisma and Hasura are very different! Prisma is a database toolkit that's used by application developers to develop server-side applications in Node.js and TypeScript (e.g. REST APIs, microservices, gRPC calls, GraphQL APIs, ..., anyth
7. 67.▲
   by nikolasburk 6y ago

   Nikolas from the Prisma team here, thanks a lot for your comment! > The problem with this tool, like every other multi-SQL-flavor-SQL ORM and query builder, is that it requires users to learn yet another language. In addition to Node.js
8. 68.▲
   by nikolasburk 7y ago

   Hey there, thanks a lot for the feedback! As I mentioned in other threads, you can configure the output location for the generated Prisma Client library [1], node_modules is just the default . The reason why we made it the default is becau
9. 69.▲
   by nikolasburk 7y ago

   > I was really excited when Prisma1 came out. It would be understatement to mention that Prisma1 was way overpromised and nothing ever materialised. While I can understand your sentiment, I don't think this is quite true! We've
10. 70.▲
    by nikolasburk 7y ago

    pgtyped looks awesome, fantastic work! We're huge fans of type-safety at Prisma so anything that makes working with DBs type-safe is right down our alley! :D I think one thing that distinguishes Prisma (on the longer run) from a librar
11. 71.▲
    by nikolasburk 7y ago

    Prisma Client is generated into node_modules by default (because that's the most familiar thing for JS/TS devs), but you can specify any target location you like for it: https://www.prisma.io/docs/reference&
12. 72.▲
    by nikolasburk 7y ago

    Massive is great and we certainly took some inspiration from it (in fact we're friends with Dian, the author of Massive and are fans of her works). The level of type-safety when using Prisma Client with TypeScript is indeed a major fac
13. 73.▲
    by nikolasburk 7y ago

    Yeah, we just published the new website today and moved around a ton of stuff. We're still in the process of cleaning things up here and there, feel free to ping me when you find more broken links :) (@nikolasburk on Twitter or Prisma
14. 74.▲
    by nikolasburk 7y ago

    Hey, thanks a lot for the feedback (and I've seen harsher words on HN, so no worries)! I wrote most of the docs, so more than happy to take any feedback to see where it can improved! What I'm mostly trying to refer to are ActiveRe
15. 75.▲
    by nikolasburk 7y ago

    You can specify where you want to generate Prisma Client yourself, `node_modules` it's just the default. See my response above: > Also note that you can actually generate Prisma Client into a different location [4], so if you prefer
16. 76.▲
    by nikolasburk 7y ago

    I don't believe so, this term was coined by one of our community members and we really liked it and decided to adopt it to distinguish Prisma Client conceptually from "conventional" (for lack of a better term) node modules.
17. 77.▲
    by nikolasburk 7y ago

    Depending on your deployment environment and workflow, there indeed can be special requirements wrt deployment (also because Prisma Client relies on a "query engine binary" [1] which needs to run as a side-process on the same mach
18. 78.▲
    by nikolasburk 7y ago

    Nikolas from Prisma here, a realtime API for Prisma is certainly on our roadmap – as Prisma doesn't provide a GraphQL interface, this most likely will not come in the form of GraphQL subscriptions though but another (programmatic) real
19. 79.▲
    by nikolasburk 7y ago

    Prisma and Hasura are very different! Prisma is a database toolkit that's used by application developers to develop server-side applications in Node.js and TypeScript (e.g. REST APIs, microservices, gRPC calls, GraphQL APIs, ..., any
20. 80.▲
    by nikolasburk 7y ago

    Hey! Thanks a lot for sharing this, a lot of the features you mention here are already possible with Prisma 2.0 (or will be in the future). Would love to hear your thoughts on the new version :)
21. 81.▲
    by nikolasburk 7y ago

    Ah thanks for catching this Martin, fixed!
22. 82.▲
    by nikolasburk 7y ago

    https://twitter.com/mojombo/status/1244877311196856320
23. 83.▲
    by nikolasburk 7y ago

    We're indeed planning to broaden the support for various databases in the future (e.g. already looking into MongoDB and FaunaDB). If you have a specific DB in mind that you'd like to see supported, please open a feature request he
24. 84.▲
    by nikolasburk 7y ago

    Thanks, will get that fixed!
25. 85.▲
    by nikolasburk 7y ago

    We are planning to eventually add commercial cloud services to make Prisma/DB workflows easier (especially for teams and larger organizations). The current OSS database toolkit will remain free forever! More info here: https:/&#x
26. 86.▲
    by nikolasburk 7y ago

    Hey! We will provide upgrade guides and dedicated tooling [1] in the next couple of weeks to ensure a smooth transition for current Prisma 1 users! You can find more context on isprisma2ready.com. [1] https://github.com/pris
27. 87.▲
    by nikolasburk 7y ago

    Nikolas from the Prisma team here. The most important thing to note here is that Prisma Client is not an ORM! [1] Prisma doesn't map classes to tables as ORMs do and therefore doesn't suffer from the object-relational impedance mi
28. 88.▲
    by nikolasburk 7y ago

    Nikolas from the Prisma team here, thanks a lot for the shoutout! For people who want to learn more about using Prisma together with Nexus (which enables exposing DB models via GraphQL), I also recommend checking the next iteration of Nexus
29. 89.▲
    by nikolasburk 7y ago

    Nikolas from the Prisma team here! > It seems to take a lot of inspiration from the mongo api That's an interesting comment but I'm not sure it's quite accurate. I think where we're taking quite a bit of inspiration f
30. 90.▲
    by nikolasburk 7y ago

    Indeed! It's already usable though, we have an online demo here: https://prisma-studio.now.sh/