refactor: upgrade hibernate dialect

[jo-elimu]

Issue Number

• Resolves Upgrade Hibernate dialect to newer version #1966

Purpose

• Needed when upgrading to Hibernate 6.

Technical Details

Testing Instructions

• Deploy release and test changes.

Screenshots

---

Format Checks

Note

Files in PRs are automatically checked for format violations with mvn spotless:check.

If this PR contains files with format violations, run mvn spotless:apply to fix them.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 16.05%. Comparing base (60bf9f8) to head (2b63491).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
.../ai/elimu/web/servlet/CustomDispatcherServlet.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #1967   +/-   ##
=========================================
  Coverage     16.05%   16.05%           
  Complexity      483      483           
=========================================
  Files           257      257           
  Lines          7824     7824           
  Branches        804      804           
=========================================
  Hits           1256     1256           
  Misses         6518     6518           
  Partials         50       50           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Walkthrough

The pull request focuses on upgrading the Hibernate dialect across multiple configuration files from the deprecated MySQL5Dialect to the newer MySQLDialect. This change involves updating the dialect settings in the CustomDispatcherServlet, jdbc_PROD.properties, and jdbc_TEST.properties files. Additionally, the jpa-schema-export.sql file has been modified to update table engine specifications and expand column sizes to support larger text data.

Changes

File	Change Summary
src/main/java/ai/elimu/web/servlet/CustomDispatcherServlet.java	Updated Hibernate dialect from MySQL5Dialect to MySQLDialect
src/main/resources/jdbc_PROD.properties, src/main/resources/jdbc_TEST.properties	Updated jpa.databasePlatform to use MySQLDialect
src/main/resources/META-INF/jpa-schema-export.sql	- Replaced engine=MyISAM with type=MyISAM for all tables - Expanded column sizes from varchar(1000) to longtext for multiple columns

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade Hibernate dialect [#1966]	✅
Backup databases [#1966]	❓	No evidence of database backup in the PR
Release and deploy changes [#1966]	❓	Deployment process not shown in the PR
Test database structure changes [#1966]	❓	No explicit testing evidence provided

Possibly related issues

• Set correct Hibernate database dialect for exporting the JPA schema #1696 (Set correct Hibernate database dialect for exporting JPA schema)
  • The changes in this PR partially address the dialect configuration, though the specific schema export configuration is not fully resolved

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 60bf9f8 and 2b63491.

📒 Files selected for processing (4)

• src/main/java/ai/elimu/web/servlet/CustomDispatcherServlet.java (1 hunks)
• src/main/resources/META-INF/jpa-schema-export.sql (21 hunks)
• src/main/resources/jdbc_PROD.properties (1 hunks)
• src/main/resources/jdbc_TEST.properties (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: build (windows-latest, 21)
• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (ubuntu-latest, 21)
• GitHub Check: build (ubuntu-latest, 17)
• GitHub Check: test_ui_ENG

🔇 Additional comments (4)

src/main/java/ai/elimu/web/servlet/CustomDispatcherServlet.java (1)

74-74: LGTM! Dialect update aligns with Hibernate 6 upgrade.

The change from MySQL5Dialect to MySQLDialect is correct. MySQLDialect is the recommended dialect in Hibernate 6, which automatically adapts to the MySQL version in use.

src/main/resources/jdbc_PROD.properties (1)

3-3: LGTM! Production database platform configuration updated correctly.

The JPA database platform update is consistent with the Hibernate 6 upgrade and matches the dialect change in CustomDispatcherServlet.

src/main/resources/jdbc_TEST.properties (1)

3-3: LGTM! Test database platform configuration updated correctly.

The JPA database platform update maintains consistency with the production configuration and Hibernate 6 requirements.

src/main/resources/META-INF/jpa-schema-export.sql (1)

165-165: LGTM! Column type changes improve data capacity.

The changes from varchar to longtext for various text fields are appropriate:

• Improves capacity for potentially large text content
• No risk of data loss
• Consistent approach across similar fields

Also applies to: 208-208, 220-220, 233-233, 253-253, 296-296, 337-337, 360-360, 371-371, 408-408, 420-420, 448-448, 460-460, 491-491, 507-507, 509-509, 526-526, 530-530, 531-531, 539-539, 553-553, 569-569, 601-601, 641-641, 676-676, 687-687, 701-701