Issues integrating into existing Microsoft SQL database about zenstack HOT 9 CLOSED

Hi @levipro , thanks for reporting this! Currently @default doesn't support the second argument yet. I think you can workaround using the @prisma.passthrough attribute:

CreatedDate  DateTime @prisma.passthrough('@default(now(), map: "DF_Address_CreatedDate")') @db.DateTime

from zenstack.

Thanks @ymc9 is there any work around for

NVarChar(Max)
VarChar(Max)

from zenstack.

Thanks @ymc9 is there any work around for

NVarChar(Max) VarChar(Max)

Sorry I missed that part. I'm actually not sure where this error came from. Do you mind sharing the zmodel snippet that caused it? Thanks! @levipro

from zenstack.

Here is an example repo
https://github.com/levipro/zenstack-issue

pnpm zenstack generate
Validation errors:
line 20: Could not resolve reference to ReferenceTarget named 'Max'. [Max]
line 21: Could not resolve reference to ReferenceTarget named 'Max'. [Max]
line 20: Value is not assignable to parameter [Max]
line 21: Value is not assignable to parameter [Max]
line 20: expression cannot be resolved [Max]
line 21: expression cannot be resolved [Max]

from zenstack.

I see. You can use the same "@prisma.passthrough" attribute to workaround. It basically passes text directly to the generated prisma schema:

Latitude                 String? @prisma.passthrough('@db.VarChar(Max)')

from zenstack.

Hi @levipro , I'm working on fixing this but couldn't find Prisma's documentation for the @db.VarChar(Max) definition (for the Max enum). Just wondering you may know where it's documented. I want to make sure to add other missing definitions as well.

from zenstack.

I don't have much information on that, maybe these might be a little help:
https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference
https://www.prisma.io/dataguide/datamodeling/tables-tuples-types

from zenstack.

Thanks! Finally found something in a link to Microsoft's doc. It seems Max is the only missing thing for that part.

from zenstack.

Hi @levipro , both issues are fixed in v1.1.0

from zenstack.