PostGIS is a very popular extension for Postgres. Please consider supporting this when designing the new Postgres API.
The PostgreSQL connector issue is https://github.com/graphcool/prisma/issues/1641. Let's keep this issue to discuss PostGIS support :-)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Should remain open, thanks Probot.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.
+1
+1
+1
PostGIS support asp please
+1
+1
+1 Please we need support for PostGIS.
PostGIS support would be great.
+1
+1
+1
+1
for anyone interested, i think this issue is old and part of prisma1 which is in "maintenance mode".
i found issues for prisma2, which seems like they're getting closer to adding in some initial support:
๐ https://github.com/prisma/prisma/issues/2789
๐ https://github.com/prisma/prisma/issues/1798
๐ https://github.com/prisma/prisma/issues/3447
Really looking forward to this! +1
+1
We are not using prisma because of this. So +โ
We are not using prisma because of this. So +โ
@francescortiz what did you guys decide to roll with instead? ๐
We went for MikroORM, because we can use @Formula
for custom values: https://mikro-orm.io/docs/defining-entities#formulas. Also, being able to manually extend the models (entities) is a nice feature.
Moreover, if we need to extend it, we don't have a proficient team in rust by now, so we would have been completely dependent on you.
But the experience with prisma was awesome! I would have loved to stay with it. Specially because of the beauty with which cursors are handled.
Looks like I'll have to try a different ORM for my Next.js mapping project. So +1 from me.
Most helpful comment
Should remain open, thanks Probot.