feat: implement rich metadata relational schema with Drizzle ORM#572
Open
dev-fatima-24 wants to merge 1 commit intoHahfyeex:Defaultfrom
Open
feat: implement rich metadata relational schema with Drizzle ORM#572dev-fatima-24 wants to merge 1 commit intoHahfyeex:Defaultfrom
dev-fatima-24 wants to merge 1 commit intoHahfyeex:Defaultfrom
Conversation
|
@dev-fatima-24 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Owner
|
@dev-fatima-24 pls resolve conflicts |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request: Implement Rich Metadata Relational Schema
Description
This PR implements the relational database schema required to store "Rich Metadata" (categories, long-form descriptions, and image pointers) that is too resource-intensive to maintain directly on the Stellar blockchain.
While the core financial operations (payouts/bets) remain on-chain via Soroban, this off-chain layer provides a premium user experience with detailed market context and organized discovery.
Key Changes
pgfor type-safe, performant Postgres interactions.markets: Core market metadata with a Unique Index on the Sorobancontract_id.categories: Taxonimized organization for market discovery.user_profiles: Rich metadata (bio, avatar, username) for Stellar wallet holders.src/db/utils.jsfor clean CRUD operations on metadata.scripts/seed.jsto populate the environment with initial categories and profiles.tests/db_utils.test.jsandtests/seed_script.test.js.Visual Schema Validation
Verification Steps
npm run seed # or node scripts/seed.jsnpm run test -- tests/db_utils.test.js tests/seed_script.test.js --coverageChecklist
/docs/database.md.Closes #8