Getting P1012 preview feature not found using fullTextSearchPostgres
Using Prisma v6, when attempting to reset the my Postgres DB using
prisma migrate reset --force
, I am receving the following error:
I have tried clearing all modules and caches, re-generating client, etc. At a loss as to why this happening and how to fix.4 Replies
You opted for speed from this bot. Let's conjure up an answer right now!
Based on the information provided in the knowledge sources, I can help explain the issue you're encountering and suggest a solution.
The error you're seeing (P1012) indicates that the preview feature "fullTextSearchPostgres" is not recognized by your current version of Prisma. This is because in Prisma v6, the full-text search feature for PostgreSQL has been renamed.
According to the Upgrade to Prisma ORM 6 documentation, the
fullTextSearch
Preview feature has been promoted to General Availability for MySQL, but it remains in Preview for PostgreSQL. For PostgreSQL users, the feature flag has been renamed to fullTextSearchPostgres
.
To fix this issue, you need to update your schema.prisma
file. Replace fullTextSearchPostgres
with fullTextSearch
in your previewFeatures
array. Here's how your generator block should look:
After making this change, try running your prisma migrate reset --force
command again. It should resolve the P1012 error.
For future reference, you can always check the list of currently active Preview features in the Prisma Client & Prisma schema documentation. This page is regularly updated with the latest available preview features.
If you continue to experience issues after making this change, please ensure that you have the latest version of Prisma installed, as feature flags can sometimes change between versions.
🤔 Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly.
In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.Hi @Scott
Can you please share your Prisma Schema and the steps you took to perform the
prisma migrate reset
command?here is the root schema, as I'm using multischema as well. I'm simply running
prisma migrate reset --force
@RaphaelEtim any update on this?