Open rickdoesdev opened 2 years ago
Whats up Rick, my work around is to put the @db.Money or @db.Text in the base.prisma of the destination and exclude it from the imported model.
While that obviously works because it all winds up merged at the end, it's now breaking the clean boundaries of having data domains split out that lead to using aurora in the first place!
If I have a column type of Decimal @db.Money in one of the schemas I'm importing in my aurora.config.json to merge, I get a panic from rust
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect the ./prisma/schema.prisma to be generated correctly
Desktop (please complete the following information):
tool version "prisma-aurora": "^1.3.5",
Additional context I can work around this by including a duplicate
datasource db { provider = "postgres" url = env("DATABASE_URL") }
into the second schema file, but it does mean I'm now having to declare this in every file that might be using this extended native type