Issues: prisma/prisma1-upgrade
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
https://binaries.prisma.sh/all_commits/ not found when installing library.
#156
opened Apr 15, 2024 by
grayback6192
ERROR 1175 (HY000) at line 2: You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column.
kind/improvement
#124
opened Jan 15, 2022 by
janpio
Last step of the prisma upgrade cli adds duplicates and unnecessary data
#113
opened May 30, 2021 by
JackieJoo
Support a schema only translation for Prisma 1 MongoDB users
#104
opened Feb 25, 2021 by
matthewmueller
last step adds @map attribute to relation fields + it wrongly renames some relation fields
#103
opened Feb 24, 2021 by
omar-dulaimi
upgrade cli does not distinguish that a field is ENUM and not a MEDIUMTEXT
#102
opened Feb 20, 2021 by
omar-dulaimi
Is the "All non-inline relations are recognized as m-n" workaround correct?
#98
opened Jan 26, 2021 by
AikoRamalho
Prisma-upgrade produces duplicates for relations: Field 'X' is already defined on modal 'Y'
#97
opened Jan 19, 2021 by
runar-indico
Missing column error for ALTER TABLE
File
ADD UNIQUE (logoCompany
);
#89
opened Oct 20, 2020 by
henryson
Several errors in schema.prisma after full migration from 1.29 -> prisma 2
#85
opened Sep 17, 2020 by
Karnich
ERROR: default for column "role" cannot be cast automatically to type "dr3$dev"."Role"
#84
opened Sep 17, 2020 by
nikolasburk
Previous Next
ProTip!
Follow long discussions with comments:>50.