Skip to content

Change team column to text on coplan_users #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HamptonMakes merged 1 commit into from
Apr 3, 2026
Merged

Change team column to text on coplan_users #81

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions engine/db/migrate/20260404000000_change_team_to_text_on_coplan_users.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
class ChangeTeamToTextOnCoplanUsers < ActiveRecord::Migration[8.1]
def up
change_column :coplan_users, :team, :text
end

def down
change_column :coplan_users, :team, :string
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Make rollback resilient to long team values

The down migration narrows coplan_users.team back to string (VARCHAR(255)), but this migration exists specifically because real team paths now exceed 255 chars. In MySQL strict mode, rolling back after any long value is written will fail with Data too long, which can block an emergency deploy rollback. Consider making down explicitly irreversible or truncating/cleaning oversized rows before the type change so rollback can complete predictably.

Useful? React with 👍 / 👎.

end
end