fix: resolve missing column references in admin stats queries#650
Merged
Conversation
- Remove engagement_reasons column from queries (computed dynamically, not stored) - Fix next_step/next_step_due_date references to use org_activities table - Fix stripe_subscription_status to use correct subscription_status column These columns were queried from the organizations table but either: 1. Don't exist (engagement_reasons is computed in functions) 2. Are on a different table (next_step fields are on org_activities) 3. Have a different name (subscription_status not stripe_subscription_status) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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
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.
Summary
engagement_reasonscolumn from queries (computed dynamically, not stored)next_step/next_step_due_datereferences to useorg_activitiestable via LATERAL joinstripe_subscription_statusto use correctsubscription_statuscolumnRoot Cause
The production error
column "engagement_reasons" does not existin/api/admin/my-prospectswas caused by queries referencing columns that either:engagement_reasonsis computed in functions, not stored)next_stepfields are onorg_activities, notorganizations)subscription_statusnotstripe_subscription_status)Test plan
npm run build)npm run typecheck)npm test)🤖 Generated with Claude Code