Skip to content

feat: Use Prisma instead of PG for DB abstraction #4

New issue

Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “No Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? No Sign in to your account

Merged
merged 2 commits into from
Jun 11, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Postgres support for Kapeta

Uses Prisma to make it simple to work with Postgres from Kapeta - and
add support for DB migrations.

Also exposes a CLI tool called ```kap-postgres-url``` that can be used
to generate a PG database URL from within a Kapeta block - for a given environment.


191 changes: 55 additions & 136 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 3 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@kapeta/sdk-sqldb-postgresql",
"version": "1.1.1",
"description": "",
"description": "Kapeta SDK for PostgreSQL",
"main": "index.js",
"private": false,
"publishConfig": {
Expand Down Expand Up @@ -59,7 +59,8 @@
]
},
"dependencies": {
"pg": "^8.8.0"
"@prisma/client": "^4.15.0",
"prisma": "^4.15.0"
},
"devDependencies": {
"@kapeta/sdk-config": "<2",
Expand Down
Loading