rubyforgood / rubyforgood/skillrx-beacon
Database Schema Updates for Sync Tracking
Open
Nobody has claimed this yet.
cross-app sync
- Dominant language
- HTML
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Add external IDs and checksums for sync tracking
- Add migration for topic_files:
add_column :topic_files, :external_id, :integer
add_column :topic_files, :external_checksum, :string
add_index :topic_files, :external_id, unique: true
- Add migration for topics:
add_column :topics, :external_id, :integer
add_index :topics, :external_id, unique: true
- Add migration for content_providers:
add_column :content_providers, :external_id, :integer
add_index :content_providers, :external_id, unique: true
- Add migration for tags:
add_column :tags, :external_id, :integer
add_index :tags, :external_id, unique: true
Do the same thing for whatever entities we would like to sync
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing schema and migrations for topic_files, topics, content_providers, and tags, then identify any other entities that must participate in sync tracking. Add the requested external identifiers, checksum, and unique indexes for the agreed entities, and verify the migrations apply cleanly and produce the intended schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100