prisma-client-py
prisma-engines
prisma-client-py | prisma-engines | |
---|---|---|
11 | 10 | |
1,618 | 1,100 | |
- | 2.0% | |
9.0 | 9.7 | |
7 days ago | 4 days ago | |
Python | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prisma-client-py
-
Sunday Daily Thread: What's everyone working on this week?
almost samezies, although I'm trying prisma-client-py for team-specific reasons.
-
Alternatives to SQLAlchemy for your project - Prisma case
Anyway, prisma is a relatively new project, and it is very pleasant to use. I encourage you to give it a try and support the python client (at least a star on GitHub). For me who doesn't like SQL, being able to retrieve models from the database and make queries with prisma is a breath of fresh air. 🤣
-
A beginners guide to building a Flask API with Prisma
I really enjoyed using Prisma in javascript, and I am glad that Robert created a client for python. 🔥🔥
-
Show HN: Prisma Python – A fully typed ORM for Python
Thanks for the suggestion, I've created an issue to track this as I do agree that `ANY` conveys the operation more clearly.
https://github.com/RobertCraigie/prisma-client-py/issues/293
- GitHub - RobertCraigie/prisma-client-py: Prisma Client Python is an auto-generated and fully type-safe database client
- Type safe database access for Python – Prisma Client Python
- Type safe ORM for Python – Prisma Client
-
Prisma Client Python - Type safe database access
Prisma Client Python is an easy to use, fully typed ORM that supports SQLite, PostgreSQL, MongoDB, MySQL and SQL Server!
prisma-engines
-
We migrated to SQL. Our biggest learning? Don't use Prisma
This is a very strange comment section. And this article is insanely poorly written.
> Last week, we completed a migration that switched our underlying database from MongoDB to Postgres.
Okay cool, but why? MongoDB is a very capable and fast database.
> It was a shock finding out that Prisma needs almost a “db” engine layer of its own. Read more about it here: https://www.prisma.io/docs/concepts/components/prisma-engine...
If you did any research on Prisma rather than diving in head-first, you'd realize this is a core part of why Prisma exists.
> we discovered that at a low level, Prisma was fetching data from both tables and then combining the result in its “Rust” engine. This was a path for an absolute trash performance.
Can you confirm this is actually the case? Can you show some benchmarks re: this claim? Or are you just assuming this is the case?
-
Prisma laying off 28% staff
If you wish to auto-generate migrations, there are declarative schema change tools available for most relational databases. I'm the creator of Skeema [1] which provides them for MySQL, but there are options for other DBs too [2][3][4].
Prisma's migration system actually partially copied Skeema's design, while giving credit in a rather odd fashion which really rubbed me the wrong way: "The workflow of working with temporary databases and introspecting it to determine differences between schemas seems to be pretty common, this is for example what skeema does." [5]
While I doubt I was the first person to ever use that technique, I absolutely didn't copy it from anywhere, and it was never "pretty common". I'm not aware of any other older schema change systems that work this way.
[1] https://www.skeema.io
[2] https://github.com/djrobstep/migra
[3] https://github.com/k0kubun/sqldef
[4] https://david.rothlis.net/declarative-schema-migration-for-s...
[5] https://github.com/prisma/prisma-engines/blob/6be410e/migrat...
-
Maintenance of popular ORMs (explanation inside)
If you're serious about your review then you shouldn't ignore the fact that Prisma has a big blob of Rust code at its core, where other ORMs use standard database adapters from NPM. As someone who has maintained database adapters for other languages, let me tell you that the maintenance burden of that is quite significant. Especially if they ever want to support more advanced database features. If the company behind Prisma ever runs out of money, the project is probably toast.
- Show HN: WunderBase – Serverless OSS Database on Top of SQLite, Firecracker
-
If Prisma's query engine is compiled by Rust, why don't I need Rust to compile it?
prisma generate generates the code for the Prisma client. The code generated for the client is all JavaScript which calls into the “Prisma Engine” Rust native Node module to perform database operations. As others here have said, the Prisma Engine is pre-compiled by rustc via CI and gets dowloaded to your machine as a pre-built binary by npm, so there’s no need for you to build it yourself by running the Rust compiler locally.
-
Alternatives to SQLAlchemy for your project - Prisma case
Note: you may notice that it downloads some binaries when you first invoke this command. This is normal it fetches the node prisma cli and engines used by prisma. 😁
-
I went about learning Rust
We solved this with flat vectors and just sharing index values in cheap walker objects. It is much nicer to work with compared to arc/weak pointers.
Code here: https://github.com/prisma/prisma-engines/tree/main/libs%2Fda...
-
Show HN: Prisma Python – A fully typed ORM for Python
Because Prisma Python currently interfaces with the Rust engine over HTTP (I am looking into changing this) and the Rust engines can be found here:
https://github.com/prisma/prisma-engines
-
MariaDB to go public at $672M valuation
Thanks! I know of a couple Postgres tools that work in a declarative fashion: migra [1] and sqldef [2].
Migra is Postgres-specific. Its model is similar to Skeema's, in that the desired-state CREATEs are run in a temporary location and then introspected, to build an in-memory understanding of the desired state which can be diff'ed against the current actual state. (This approach was also borrowed by Prisma Migrate [3]). In this manner, the tool doesn't need a SQL parser, instead relying on the real DBMS to guarantee the CREATE is interpreted correctly with your exact DBMS version/flavor/settings.
In contrast, sqldef supports multiple databases, including Postgres and MySQL (among others). Unlike other tools, it uses a SQL parser-based approach to build its in-memory understanding of the desired state. As a DB professional, personally this approach scares me a bit, given the amount of nonstandard stuff in each DBMS's SQL dialect. But I'm inherently biased on this topic. And I will note sqldef's author is a core Ruby committer and JIT author, and is extremely skilled at parsers.
[1] https://databaseci.com/docs/migra
[2] https://github.com/k0kubun/sqldef
[3] https://github.com/prisma/prisma-engines/blob/main/migration...
-
Prisma 2 - When Can I Use it Alone and When Should I add Graphql
Prisma 2 is a program, written in Rust that exposes a GraphQL API on top of your database of choice. Here's a link to the "engine": https://github.com/prisma/prisma-engines
What are some alternatives?
SQLAlchemy - The Database Toolkit for Python
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines
tortoise-orm - Familiar asyncio ORM for python, built with relations in mind
migra - Like diff but for PostgreSQL schemas
PonyORM - Pony Object Relational Mapper
sqldef - Idempotent schema management for MySQL, PostgreSQL, and more
Peewee - a small, expressive orm -- supports postgresql, mysql, sqlite and cockroachdb
gopy - gopy generates a CPython extension module from a go package.
Piccolo - Piccolo (formerly Pilot) – mini game engine for games104
prisma-client-rust - Type-safe database access for Rust
pydantic-redis - A simple Declarative ORM for Redis using pydantic Models
pocketbase - Open Source realtime backend in 1 file