Type Aliases not working

[yovanoc]

Hello I see since one of the latest alpha I can't use my custom type.

PS: this error happen while prisma2 lift up

[pantharshit00]

I can confirm this bug.

[mavilein]

I cannot reproduce this with the following version:

➜  type-alias-test prisma2 version
prisma2@2.0.0-preview015, binary version: 20b6dc13949cccccfef5be07c0be7a3d7c858abe

[mavilein]

Nevermind my comment. I forgot -g in my npm install command 🤦‍♂

[mavilein]

This is a regression of our new approach of diffing datamodels. The new diffing algorithm cannot handle type aliases as of now.

[tomhoule]

This should be fixed by prisma/prisma-engines#183. The fix will be in prisma2@alpha soon, and in the next preview version :)

[tomhoule]

I'll close the issue, but feel free to re-open if the problem persists.

[yovanoc]

still happening to me with prisma2@2.0.0-alpha.334, binary version: b72fd0a786adc77ba6c61d0a9637ff0371e433b0

[tomhoule]

Oh :/ Does the custom type appear in the migration when you prisma2 lift save?

[yovanoc]

No, that's why I get this error I guess

[pantharshit00]

I can confirm this still occurs in prisma2@2.0.0-alpha.338, binary version: b72fd0a786adc77ba6c61d0a9637ff0371e433b0

[tomhoule]

I just double checked and your binary version (b72fd0a786adc77ba6c61d0a9637ff0371e433b0) is older than the fix - the new preview that is coming out soon should have the fix.

[janpio]

@pantharshit00 Can you please double check if this occurs with the new preview017 release?

[pantharshit00]

Ok, I am not able to reproduce this now with preview-017.

Also, a quick note that you will need to delete the migrations both from the database and locally. They contain the wrong steps.

[nhuesmann]

Related to this issue, in Preview 17 I have been having a weird issue with custom types. I'm using the same type alias as the issue creator (CUID as an abstraction of String @id @default(cuid())). When I try to perform a migration with prisma2 lift up, I get an error stating that type CUID already exists—it seems like regardless of the changes I make to my schema, the lift up operation is trying to recreate the custom type.

[pantharshit00]

@nhuesmann I can confirm that bug.

I opened a new issue about there here: prisma/migrate#225

[nhuesmann]

@pantharshit00 great, thank you!