Skip to content

Next generations #24674

Description

@introvert

Bug description

Are you sure this a "next generation" ORM? It cannot be even set up with the basic postgresql providers after hours of buggling with the configuration.

Not even "db:push" can be properly completed in a normal dev environment, which makes us question whether we should continue bothering with the "next generation" project.

Are you guys sure that you know what meaning words have and the dissonance between the contemporary marketing of tooling vs reality of things?

How to reproduce

Expected behavior

Exactly as described.

Prisma information

// Add your schema.prisma
// Add your code using Prisma Client

Environment & setup

  • OS:
  • Database:
  • Node.js version:

Prisma Version


Activity

  1. apolanc commented on Jul 4, 2024

    @apolanc
    Contributor

    Hi, this is not a very nice way to introduce yourself @introvert and appreciate what open source teams and projects offer the community and the effort put behind it.

    Now, focusing on the actual problem: Could you explain the problem a little better and share some of the necessary information so that we can verify it and support you (environment and configuration, your schema file, etc.)? That would be greatly appreciated.

  2. locked and limited conversation to collaborators on Jul 8, 2024
  3. converted this issue into a discussion #24725 on Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions