fix: flask db check fails due to nullable mismatch between migrations and models

[ltoppyl]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Update SQLAlchemy model definitions to use Mapped[T | None] with explicit nullable=True for columns where the database allows NULL values but the ORM previously implied NOT NULL.

Affected columns:

• app_triggers.provider_name
• operation_logs.content
• providers.quota_used

This resolves flask db check validation failures in CI/CD workflows.

Close #30473

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @ltoppyl, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an inconsistency between SQLAlchemy model definitions and the underlying database schema. By explicitly marking certain columns as nullable in the ORM, it ensures that the Python models accurately reflect the database's allowance for NULL values. This correction is crucial for maintaining data integrity and resolves validation errors encountered during database checks in the CI/CD pipeline.

Highlights

• Model Type Hint Alignment: Updated SQLAlchemy model definitions to explicitly align type hints with database nullable constraints, using Mapped[T | None] for columns that allow NULL values.
• Specific Column Adjustments: Applied these adjustments to app_triggers.provider_name, operation_logs.content, and providers.quota_used to reflect their nullable status in the database.
• CI/CD Validation Fix: Resolved flask db check validation failures that were occurring in CI/CD workflows due to the previous ORM implying NOT NULL for these columns.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aligns SQLAlchemy model type hints with their corresponding database column nullability constraints. The changes correctly update operation_logs.content, providers.quota_used, and app_triggers.provider_name to be nullable, which resolves validation failures and improves the accuracy of the ORM models. The modifications are clear, targeted, and effectively address the issue. The code quality is good, and I have no further suggestions.

[crazywoola]

A migration command is needed I guess?

[crazywoola]

cc @laipz8200

[ltoppyl]

@crazywoola

As I understand it, a migration shouldn't be required here. We are only updating the model definitions to reflect the current state of the database. Since the DB schema itself remains the same, running a migration command shouldn't be necessary.