Skip to content
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

Unable to migrate from v0.1.0 to v0.2.0 #80

Open
wesleykirkland opened this issue Feb 23, 2025 · 0 comments
Open

Unable to migrate from v0.1.0 to v0.2.0 #80

wesleykirkland opened this issue Feb 23, 2025 · 0 comments

Comments

@wesleykirkland
Copy link
Contributor

From v0.1.0 to v0.2.0 theres been a large feature addon with the onboarding section and a migration from v0.1.0 to v0.2.0 seems to be impossible.

Getting to the point, the automatic Prisma schema migration fails due to providerId not being set in LLMProvider, I'm able to load up a DBClient and set this and load up the correct values. From there, I receive a successful message in the logs stating that the migration can proceed and that my schema is now in sync.

Upon logging in my end result is the following. I have all of my health data and previous chats already stored and want to be able to use them going forward.

App Logs

prisma:error 
Invalid `prisma.assistantMode.findFirstOrThrow()` invocation:
An operation failed because it depends on one or more records that were required but not found. Expected a record, found none.
 ⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.assistantMode.findFirstOrThrow()` invocation:
An operation failed because it depends on one or more records that were required but not found. Expected a record, found none.
    at async d (.next/server/app/page.js:1:5724) {
  code: 'P2025',
  clientVersion: '6.4.1',
  meta: [Object],
  digest: '2260083970'
}

End User Web

Application error: a server-side exception has occurred (see the server logs for more information).
Digest: 2260083970

Desired outcome: How can I upgrade from v0.1.0 to v0.2.0 without data loss?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant