Enhance character set and collation for GitHub pull requests table

[guibranco]

Description

• Enhanced the github_pull_requests table to use utf8mb4 character set for better Unicode support.
• Updated collation to utf8mb4_unicode_ci for improved string comparison.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	002.create_github_pull_requests_table.sql Update character set and collation for GitHub pull requests table Sql/002.create_github_pull_requests_table.sql Updated table creation to use utf8mb4 character set. Changed collation to utf8mb4_unicode_ci. +1/-3

[deepsource-io[bot]]

Here's the code health analysis summary for commits d81c1a4..5718aa5. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Docker	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
SQL	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[penify-dev[bot]]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and primarily involve updating the character set and collation, which is a common task in database schema modifications.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Verify the suitability of the collation for the expected query behavior ___ **Ensure that the collation utf8mb4_unicode_ci is appropriate for the expected queries, as it may affect sorting and comparison behavior.** [Sql/002.create_github_pull_requests_table.sql [26]](https://github.com/guibranco/gstraccini-bot/pull/488/files#diff-ffa2290e4edd167169a20a7c2cbd3612ec0dc58c51cec9d7494ab82a261ae4a1R26-R26) ```diff -) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; +) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; -- Verify collation suitability for queries ``` Suggestion importance[1-10]: 6 Why: Verifying the suitability of collation is important for query performance, making this suggestion relevant and valuable.	6
Maintainability	Add a comment to clarify the choice of character set and collation ___ **It may be beneficial to add a comment explaining the choice of utf8mb4 and utf8mb4_unicode_ci for future reference and clarity.** [Sql/002.create_github_pull_requests_table.sql [26]](https://github.com/guibranco/gstraccini-bot/pull/488/files#diff-ffa2290e4edd167169a20a7c2cbd3612ec0dc58c51cec9d7494ab82a261ae4a1R26-R26) ```diff +-- Using utf8mb4 for full Unicode support and utf8mb4_unicode_ci for case-insensitive comparisons ) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; ``` Suggestion importance[1-10]: 5 Why: Adding a comment for clarity is a good practice, but it does not address any critical issues in the code.	5
Performance	Review the storage implications of using utf8mb4 for large datasets ___ **Consider reviewing the implications of using utf8mb4 for storage requirements, especially if the database will handle a large volume of data.** [Sql/002.create_github_pull_requests_table.sql [26]](https://github.com/guibranco/gstraccini-bot/pull/488/files#diff-ffa2290e4edd167169a20a7c2cbd3612ec0dc58c51cec9d7494ab82a261ae4a1R26-R26) ```diff -) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; +) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; -- Review storage implications ``` Suggestion importance[1-10]: 4 Why: While it's important to consider storage implications, this suggestion does not provide a direct improvement to the code itself.	4
Best practice	Ensure consistent character set application across all columns in the table ___ **Consider adding an explicit CHARACTER SET clause for the table to ensure that the character set is applied consistently across all columns.** [Sql/002.create_github_pull_requests_table.sql [26]](https://github.com/guibranco/gstraccini-bot/pull/488/files#diff-ffa2290e4edd167169a20a7c2cbd3612ec0dc58c51cec9d7494ab82a261ae4a1R26-R26) ```diff -) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci; +) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE utf8mb4_unicode_ci CHARACTER SET utf8mb4; ``` Suggestion importance[1-10]: 3 Why: The suggestion to add an explicit `CHARACTER SET` clause is unnecessary since the character set is already defined in the `DEFAULT CHARSET` clause.	3

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

3:11PM INF scanning for exposed secrets...
3:11PM INF 427 commits scanned.
3:11PM INF scan completed in 117ms
3:11PM INF no leaks found