You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 inLLMProvider
, 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
End User Web
Desired outcome: How can I upgrade from v0.1.0 to v0.2.0 without data loss?
The text was updated successfully, but these errors were encountered: