fix(model): increase TaskID varchar length to 250 for Vertex AI Veo 3.1

[BetterAndBetterII]

Vertex AI Veo 3.1 returns task_id values that can exceed 191 characters. Increase the column length to 250 to accommodate these longer IDs.

Fixes #2417

Summary by CodeRabbit

• Chores
  • Updated database infrastructure to support larger task identifiers.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The TaskID field in the Task struct has its GORM column type annotation increased from varchar(191) to varchar(250) to accommodate longer task ID strings generated by external APIs.

Changes

Cohort / File(s)	Summary
Database Schema Update model/task.go	Updated TaskID field GORM tag to increase varchar column size from 191 to 250 characters, enabling storage of longer task identifiers without truncation errors

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A column grew wide, from one-nine-one small,
To two-five-zero, the biggest of all!
Now task IDs long can rest without care,
No more data too long in the database there! 📝✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and accurately summarizes the main change: increasing TaskID varchar length from 191 to 250 characters to support Vertex AI Veo 3.1 task IDs.
Linked Issues check	✅ Passed	The pull request directly addresses issue #1905 by increasing the TaskID column length from 191 to 250 characters to accommodate longer task_id values returned by Vertex AI Veo 3.1.
Out of Scope Changes check	✅ Passed	The change is narrowly scoped and directly addresses the issue: only the TaskID field's varchar length is modified, with no extraneous changes or unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0b1a562 and a0697bc.

📒 Files selected for processing (1)

• model/task.go

🔇 Additional comments (2)

model/task.go (2)

46-46: LGTM – The GORM tag syntax is correct.

The change from varchar(191) to varchar(250) is syntactically valid and follows GORM conventions properly.

---

46-46: Clarify MySQL index key length requirements based on your database version and configuration.

The concern about varchar(250) with utf8mb4 charset requiring 1,000 bytes is valid only for InnoDB tables using ROW_FORMAT=COMPACT or REDUNDANT (which have a 767-byte index key limit). Modern MySQL versions (5.7.7+) default to ROW_FORMAT=DYNAMIC, which supports up to 3,072 bytes. Verify your MySQL configuration and either:

• Confirm your instance uses ROW_FORMAT=DYNAMIC or COMPRESSED, or
• Reduce the column size if constrained to older row formats.

For Vertex AI Veo 3.1, the task_id is a base64-encoded Google Cloud operation name (format: projects/{id}/locations/{region}/publishers/google/models/{model}/operations/{id}), which typically encodes to ~240-290 characters. The 250-character limit appears appropriately sized for this use case.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Database migration required for existing installations.

This GORM model change updates the schema definition but does not automatically alter existing database tables. Deployments with existing data will encounter MySQL Error 1406 until the column is manually resized.

Consider providing a migration script or documenting the required ALTER TABLE command for operators.

📝 Example migration command

ALTER TABLE tasks MODIFY COLUMN task_id VARCHAR(250);

Note: The exact table name should match your GORM configuration.

🤖 Prompt for AI Agents

In model/task.go around line 46, the struct tag change to
`gorm:"type:varchar(250);index"` requires a database migration for existing
installations to avoid MySQL Error 1406; add a migration step (or document it)
that runs an ALTER TABLE to modify the column size, e.g. ALTER TABLE tasks
MODIFY COLUMN task_id VARCHAR(250); and include the migration file or
instructions in the deployment docs and your migration tooling
(golang-migrate/liquibase/your choice) so deployments run the schema change
before this release.

[BetterAndBetterII]

@seefs001

[seefs001]

@seefs001

上面那个ai也给你提示了，这个是不能改的。
需要兼容低版本mysql