Chore: Update docs and rebuild metadata #32
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🚀 PromptQL Build CompleteBuild Version: Description: PR #32: Chore: Update docs and rebuild metadata |
✅ PromptQL Build AppliedBuild Version: |
robertjdominguez
added a commit
that referenced
this pull request
Aug 10, 2025
## Description Database schema migration from `docs_bot` to `pql-bot` namespace with relationship cleanup. - Standardized database naming across all components - Removed broken relationships between doc tables - Updated connection strings and schema references Previously, the project used inconsistent naming with `docs_bot` in some places and `pql-bot` in others: ```` path=db/.env.template mode=EXCERPT DATABASE_URL=postgresql://docs:password@localhost:5432/docs_bot ```` ````typescript path=db/seed.ts mode=EXCERPT INSERT INTO docs_bot.doc_content (page_url, title, description, keywords, content, is_checked) ```` Now everything uses the consistent `pql-bot` namespace: ```` path=db/.env.template mode=EDIT DATABASE_URL=postgresql://docs:password@localhost:5432/pql-bot ```` ````typescript path=db/seed.ts mode=EDIT INSERT INTO pql-bot.doc_content (page_url, title, description, keywords, content, is_checked) ```` The migration also cleaned up problematic relationships in the PromptQL metadata that were causing schema conflicts. The `content` and `embeddings` relationships between `doc_chunk` and `doc_content` tables were removed since they were mapping on `page_url` instead of proper foreign keys, which could cause data integrity issues. This creates a cleaner, more maintainable database schema with consistent naming throughout the entire stack.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Database schema migration from
docs_bottopql-botnamespace with relationship cleanup.Previously, the project used inconsistent naming with
docs_botin some places andpql-botin others:Now everything uses the consistent
pql-botnamespace:The migration also cleaned up problematic relationships in the PromptQL metadata that were causing schema conflicts. The
contentandembeddingsrelationships betweendoc_chunkanddoc_contenttables were removed since they were mapping onpage_urlinstead of proper foreign keys, which could cause data integrity issues.This creates a cleaner, more maintainable database schema with consistent naming throughout the entire stack.