protocol VS Prisma

Reserve | Remote | Full-time | https://reserve.org | Censorship resistant money, backed by Peter Thiel and Sam Altman

Early startup with traction, 500k users across three countries, >$100M monthly transaction volume on our financial platform.

Our long-term goal is to offer an alternate currency that is essentially a modernization of commodity money – a cryptocurrency backed by a basket of low-volatility real-world assets. This would provide an alternative to USD that is actually stable enough to use as money. (No, BTC is not the answer. No, algorithmic stablecoins are not the answer.)

We’re open to team members from anywhere, with preference for the Americas due to timezones.

Our github: https://github.com/reserve-protocol/protocol/pulse/monthly

Our public progress tracker for our current protocol implementation: https://bit.ly/3KqFF1F

Open roles:

- smart contracts: https://apply.workable.com/reserve/j/D409ED8CD2/

- front end: https://apply.workable.com/reserve/j/C952B5C3F4/

- back end: https://apply.workable.com/reserve/j/752DE99DC3/

- all other roles: https://reserve.org/jobs/

In the world of software development, there are two kinds of developers: those who have never had to complain about ORMs and those who have actually used them. Whether it’s Django ORM for Python, Active Record for Ruby, GORM for Golang, Doctrine for PHP, or Prisma for TypeScript, a common issue persists: writing simple queries is straightforward, but constructing complex or optimized queries can take hours, if not days.

Support for a Union type #2505

generator client { provider = "prisma-client-js" binaryTargets = ["native", "rhel-openssl-1.0.x"] } datasource db { provider = "postgresql" // NOTE: When using mysql or sqlserver, uncomment the @db.Text annotations in model Account below // Further reading: // https://next-auth.js.org/adapters/prisma#create-the-prisma-schema // https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#string url = env("DATABASE_URL") } model Post { id Int @id @default(autoincrement()) name String createdAt DateTime @default(now()) updatedAt DateTime @updatedAt createdBy User @relation(fields: [createdById], references: [id]) createdById String @@index([name]) } // ... rest of the schema

Unfortunately Prisma hasn’t supported polymorphism yet. As such, you can't use inheritance to model the entity in the same way as in your programming language, as depicted in the above class diagram. The good news is that we could intimate it using table inheritance to imitate it.

In this project I am manually declaring the data types. For better type-safety, use Prisma, which automatically generates types based on your database schema.

When you're creating a full-stack application, you'll also need to write logic to interact with your database. For relational databases like Postgres, you can do this with SQL, or an ORM like Prisma.

Prisma is a modern TypeScript-first ORM that allows you to manage database schemas easily, make queries and mutations with great flexibility, and ensure excellent type safety.

Prisma

There have been multiple feature requests to add native support for AsyncLocalStorage to Prisma, but they haven't been met with much enthusiasm from the maintainers. Some people solved it by extending and overriding the client (which is arguably prone to breaking with updates).