feat(db): add category column to cf_feedback#3
Open
AlahmadiQ8 wants to merge 1 commit into
Open
Conversation
Closes #1 - New 003_add_category.sql migration adds a category VARCHAR2(50) column to cf_feedback with default 'General' and a CHECK constraint limiting values to: General, Product, Support, Billing, Other. - Idempotent: catches ORA-01430 so reruns are safe. - Existing rows automatically pick up the default ('General'). - install.sql updated to include the new migration in its ordered run. The APEX page changes to surface the new column on the form and report will follow once the schema migration is verified in DEV. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
a874e78 to
a5c1e83
Compare
🚀 Deploy plan for this PRAfter merge to Files in this PR that affect deploymentExecution order (deploy.yml)
Static checks passed
Static validation only — no database was contacted. Real schema/import errors will surface in |
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.
Closes #1
Summary
Adds the requested
categorycolumn to the customer feedback table so thesupport team can route incoming feedback by topic.
Type of change
Deployment notes
db/migrations/003_add_category.sqland report changes will be a follow-up PR after we confirm the column lands
cleanly in DEV.
durable schema state).
Verification
validate.ymlwill run on this PR (static checks + deploy plan comment)verify.sqlconfirmscf_feedback.categorycolumn existsRollback plan
Plain SQL migrations do not auto-rollback (DDL auto-commits). If a problem
surfaces in DEV after merge:
git revert <merge-sha>+ push + PR).004_drop_category.sqlif necessary.Demo narrative
This PR is the centerpiece of the customer demo (see
docs/DEMO_SCRIPT.md,Act 2). It demonstrates the issue -> branch -> PR -> review -> merge -> deploy
flow end-to-end against a real Oracle Autonomous Database.