Hey guys, I’m sure some people already asked this before, but is there any reason why SQL / SQLLite is not on the future plans (if it isn’t)? Is DataLoader the best solution for that?

This might help. https://github.com/prismagraphql/prisma/issues/2460

so it means it’s on the roadmap?

SQL itself is definitely there lol

yes I know but I have a working project that uses sql lite and I was wondering if Prisma was an option any time soon or either use DataLoader or anything else

You may be getting terms a little crossed. Dataloader is a pattern to aggregate queries across nested nodes to avoid N+1 queries. (Basically collects all ids and sends a

...where in [ids]

query

he's asking if he should just use dataloader instead of waiting for prisma

exactly

Datalaoder + a database does not equal Prisma. I don’t get it. So I’m out. 😊

nobody is saying that @lawjolla. But using DataLoader/join-monster + DB seems to be the best option to avoid running on the round trip problem. Prisma not only solves that, also gives you a GraphQL API to access the DB. My questions were, 1. Will Prisma ever support SQLLite. The answer is Yes, as I saw it on the roadmap. So the next question would be, when? 2. If I have to use any other solution to access a SQLLite DB now, what would be the best solution for that? DataLoader or join-monster, plain access to the DB?

But dataloader is just a pattern. Elixir/Absinthe calls it “batch”. It’s like asking if you should use SQL plus higher order functions or Prisma.

DataLoader is a utility from Facebook