Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

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

By clicking “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? Sign in to your account

Licensing questions #24287

Closed
lroal opened this issue May 25, 2024 · 0 comments
Closed

Licensing questions #24287

lroal opened this issue May 25, 2024 · 0 comments

Comments

@lroal
Copy link

lroal commented May 25, 2024

Hello, I am the maintainer of another ORM, https://gitHub.com/alfateam/orange-orm .
I am considering using prisma as the migration tool as Orange ORM does not have any.
I think there are two alternatives here.

  1. Generate prisma file from Orange ORM and let the consumer handle interaction with prisma migration him/herself.

  2. Interact with prisma migration tool directly from Orange ORM not making it transient that it uses prisma - other than having to install prisma manually (npm install).

I was wondering if number 2 is violating the license terms.

@prisma prisma locked and limited conversation to collaborators May 26, 2024
@janpio janpio converted this issue into discussion #24290 May 26, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant