Skip to content

Fix Prisma datasource to use DATABASE_URL environment variable#2565

Open
marceloramirezz wants to merge 1 commit into
evolution-foundation:mainfrom
marceloramirezz:sandbox/5caa3ada-deec-4414-922a--5hn8
Open

Fix Prisma datasource to use DATABASE_URL environment variable#2565
marceloramirezz wants to merge 1 commit into
evolution-foundation:mainfrom
marceloramirezz:sandbox/5caa3ada-deec-4414-922a--5hn8

Conversation

@marceloramirezz
Copy link
Copy Markdown

@marceloramirezz marceloramirezz commented May 25, 2026

Problem\nThe Prisma schemas were hardcoded to use environment variable, but Railway's Postgres service provides . This caused authentication failures during migrations.\n\n## Changes\n- Updated to use instead of \n- Updated to use instead of \n\n## Result\nMigrations will now correctly authenticate with the database using the proper environment variable provided by Railway's database services.

📋 Description

🔗 Related Issue

Closes #(issue_number)

🧪 Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Refactoring (no functional changes)
  • ⚡ Performance improvement
  • 🧹 Code cleanup
  • 🔒 Security fix

🧪 Testing

  • Manual testing completed
  • Functionality verified in development environment
  • No breaking changes introduced
  • Tested with different connection types (if applicable)

📸 Screenshots (if applicable)

✅ Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have manually tested my changes thoroughly
  • I have verified the changes work with different scenarios
  • Any dependent changes have been merged and published

📝 Additional Notes

Summary by Sourcery

Bug Fixes:

  • Fix database authentication failures by switching Prisma MySQL and PostgreSQL datasources to use the DATABASE_URL environment variable.

## Problem\nThe Prisma schemas were hardcoded to use  environment variable, but Railway's Postgres service provides . This caused authentication failures during migrations.\n\n## Changes\n- Updated  to use  instead of \n- Updated  to use  instead of \n\n## Result\nMigrations will now correctly authenticate with the database using the proper environment variable provided by Railway's database services.
@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented May 25, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Prisma datasource configurations to read the database connection URL from the DATABASE_URL environment variable (as required by Railway) instead of a previously hardcoded/incorrect environment variable in both MySQL and PostgreSQL Prisma schemas.

File-Level Changes

Change Details Files
Switch Prisma datasource URL to use DATABASE_URL env var for all schemas.
  • Updated datasource url configuration in the MySQL Prisma schema to reference env("DATABASE_URL") instead of the old environment variable.
  • Updated datasource url configuration in the PostgreSQL Prisma schema to reference env("DATABASE_URL") instead of the old environment variable.
prisma/mysql-schema.prisma
prisma/postgresql-schema.prisma

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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

Successfully merging this pull request may close these issues.

1 participant