Update the property to fix the migration issue

[vanitha1822]

📋 Description

JIRA ID:

Update the property "spring.jpa.hibernate.ddl-auto" from none to update to automatically update the database schema to match the entities.

---

✅ Type of Change

• 🐞 Bug fix (non-breaking change which resolves an issue)

Summary by CodeRabbit

• Chores
  • Updated the application’s configuration to enable automatic updates to the database schema, ensuring that data structures remain synchronized with the application’s definitions.

[coderabbitai]

Walkthrough

The changes update Hibernate's DDL auto-generation configuration in two property files. Previously set to "none", the value has been changed to "update", enabling the application to automatically manage and update the database schema in accordance with the entity definitions during runtime.

Changes

File(s)	Change Summary
src/main/.../common_example.properties, src/main/.../application.properties	Updated spring.jpa.hibernate.ddl-auto from none to update to enable automatic schema updates.

Suggested reviewers

• drtechie

Poem

I'm a rabbit with a hop so light,
Celebrating schema changes day and night.
"Update" now leads the code parade,
Ensuring databases won’t ever fade.
With a twitch of my nose, I cheer the change,
Hop along, for progress is in range!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 40f45eb and 77f2b6b.

📒 Files selected for processing (2)

• src/main/environment/common_example.properties (1 hunks)
• src/main/resources/application.properties (1 hunks)

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

• GitHub Check: Analyze (java)
• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (2)

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

16-16: Update Hibernate DDL Auto-Generation Strategy

The property spring.jpa.hibernate.ddl-auto has been updated to update. This change enables Hibernate to automatically adjust the database schema based on the current entity mappings, which should resolve the migration issue. Please ensure that this behavior is well-tested in your target environments, as automatic schema updates can have significant effects in production if not controlled.

src/main/environment/common_example.properties (1)

17-17: Maintain Consistency in Schema Update Configuration

The change in this file updates spring.jpa.hibernate.ddl-auto to update, aligning it with the setting in application.properties. This consistency is crucial to ensure that all environments apply the same schema migration logic.

---

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

🪧 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[sonarqubecloud]

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 SonarQube Cloud