@vowen_ai Just found your tool via an older Reddit post, seems neat. Right now it seems to be free - but of course that is not really sustainable. What are your long term plans for funding development?
@nowflux_ I was suprised though how little the market (really: traffic) grew overall in the same time span (https://t.co/4YmPymyRsp, page 3, bottom left)
@nowflux Good question.
I would expect web and mobile to grow in the same general direction though.
Looking at older data, growth was def more dynamic in the past.
Sources:
https://t.co/4cIkFaMEFq
https://t.co/jDAXgtrJs1
https://t.co/Dgt2tjGj6F
https://t.co/4LGIMq6FxK
@nuxt_js Problem report: The "Try editing this page" button leads me to a error 500 on /__nuxt_studio/auth/github?code=...&state=... (had to give the app access)
@fd1az_@jonbharrell@prisma@source So you want to combine the multiple different data models for multiple databases into one Prisma schema?
What is the benefit of doing that, besides only having to do `new PrismaClient()` once? Is there some overlap between the data sources? Relations?
@fd1az_@jonbharrell@prisma Any suggestion on how else that could work?
The default 'output' for a Client generator is the same for all instances of Prisma Client you have in a project, so you have to configure all of them to use a custom 'output'.
@matteocollina@sebinsua@prisma (π @prisma here)
Is the snippet bad because we use `prisma` both for the export and global var? We can fix that.
Beyond that, can you explain what we should do instead?
(The use case of the snippet is to not create new database connections on each hot reload of `next dev`)
@Michael_Ludden@kentcdodds@glcst@prisma@tursodatabase Indeed, currently you need to create and apply migrations manually for Turso. That is not great.
But we are working on making our CLI work with databases via driver adapters (our approach to support Turso). It should just work like all the others.