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

BREAKING CHANGE - PRIOR VERSIONS WILL NOT WORK WITH THIS DATABASE #52

Merged
merged 70 commits into from
Nov 2, 2024

Conversation

rmusser01
Copy link
Collaborator

See title. Please use the database migration script to transfer the contents of the media_db.db to the new media_db.db file.
Now have notes + conversation saving + search of both through RAG.
Also Anki deck generation.
And UML-based mindmap generation.
And multi-file upload/ingestion.

Mindmap creation via PlantUML (Utilties tab) + Token counts in conversations
Wow. I thought the prior claude was getting worse. This is just a shitpile.
Save + Update + Load works in RAG / 'normal' / Stacked chat UIs
Review of Conversations occurs in the Rag Chat/Search Tab
Workflows needs to be updated as well
Backups not properly done yet, need sanity checks to prevent the wrong DB being imported/overwriting the current one.
Ditto for showing available backups.
…op level `View DB Items` tab

Is now `Search/View DB Items`.
#409 from rmusser01/dev

Removed Chats from Media DB (BREAKING CHANGE - moved to RAG QA db), Added mindmap viewing, token counts in convos, anki flashcard validation
TO RESTORE YOUR MEDIA_DB CONTENTS, USE THE MIGRATION SCRIPT -  `Helper_Scripts/DB-Related/migrate_db.py`
`python migrate_db.py --source media_summary_old.db --target media_summary_new.db --export-path .\`
DB Views Fix + new run through video
Update Windows_Install_Update.bat
More prompt fixes; but no keyword search added yet
@rmusser01
Copy link
Collaborator Author

Like the title says, breaking changes going forward. If you have items in your media DB, please use the migration script to xfr them to the new DB schema and export your saved conversations.

This should be the last time I make breaking changes to the DB Schema before hitting v1.0 . Even then, I don't currently see anymore changes occurring that will result in a migration vs 'invisible' DB Schema changes.

@rmusser01 rmusser01 merged commit 9effd18 into the-crypt-keeper:main Nov 2, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

1 participant