Skip to content
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

Add Configuration Instructions or Environment Variable for Prisma Adapter #856

Open
vczb opened this issue Dec 1, 2024 · 1 comment
Open
Assignees

Comments

@vczb
Copy link
Contributor

vczb commented Dec 1, 2024

Summary

The Prisma setup defaults to Planetscale, which causes issues for developers trying to use a local MySQL database. This issue proposes adding instructions to the CONTRIBUTING.md file or making the adapter configurable through an environment variable.

Expected Behavior

  • Developers can easily switch between Planetscale and a local MySQL database.
  • Clear instructions are provided in CONTRIBUTING.md for configuring the Prisma adapter.
  • Alternatively, the adapter is configurable via an environment variable.

Actual Behavior

  • Prisma is hardcoded to use Planetscale by default.
  • Developers need to manually remove the Planetscale-specific configuration to use a local MySQL database.
  • This can lead to confusion and extra setup time for contributors unfamiliar with Planetscale.

Steps to Reproduce the Problem

  1. Clone the repository.
  2. Attempt to set up Prisma with a local MySQL database.
  3. Notice that the Planetscale configuration must be manually removed for the local database setup to work.

Proposed Solution

  1. Add detailed instructions to CONTRIBUTING.md on how to:

    • Set up Prisma for Planetscale.
    • Configure Prisma for a local MySQL database.
  2. Update the Prisma adapter configuration to use an environment variable, such as:

    PRISMA_ADAPTER=planetscale
    
@a20hek
Copy link
Member

a20hek commented Dec 21, 2024

thanks for bringing this to our attention!
sorry for the late reply here; this issue will be resolved on priority

@a20hek a20hek self-assigned this Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants