Fix column name mismatch in StockAlertData class and v_emailstockalert table

[vanitha1822]

📋 Description

JIRA ID:

The column name in the StockAlertData class does not match the corresponding column in the v_emailstockalert table, causing an error during execution. This PR resolves the issue by aligning the column names correctly.

✅ Type of Change

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

---

Summary by CodeRabbit

• Chores
  • Updated internal data mapping for an inventory alert metric to improve consistency and accuracy.
  • These backend changes align internal reporting with current operational expectations without affecting the user experience or visible functionality.

[coderabbitai]

Walkthrough

The pull request updates the database mapping for the quantityinhandPercent field in the StockAlertData class. The annotation has been modified so that the field now maps to the "QuantityConsumedPercent" column instead of "QuantityinhandPercent". There are no changes to the field type or other properties.

Changes

File Path	Summary
src/.../StockAlertData.java	Updated @Column annotation for the quantityinhandPercent field from "QuantityinhandPercent" to "QuantityConsumedPercent".

Poem

Hop, hop, in my code I play,
A column change lights up my day.
From in-hand to consumed in a blink,
A mapping tweak made me stop and think.
Carrots and code, together we sync!
🥕🐇

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/main/java/com/iemr/common/data/email/StockAlertData.java (1)

80-82: Column name updated correctly, but field name should be aligned with column semantics.

The column mapping has been correctly updated from "QuantityinhandPercent" to "QuantityConsumedPercent" to match the database view. This fixes the reported error in the PR objectives.

However, there's a semantic inconsistency between the Java field name quantityinhandPercent (suggesting "quantity on hand") and the column name it now maps to QuantityConsumedPercent (indicating "quantity consumed"). These represent opposite concepts that could confuse developers.

Consider renaming the field to match the column semantics:

  @Column(name = "QuantityConsumedPercent")
  @Expose
- private Double quantityinhandPercent;
+ private Double quantityConsumedPercent;

Additionally, the current field name doesn't follow proper Java camelCase convention (should be quantityInHandPercent if keeping the current name).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 482f441 and 7516be5.

📒 Files selected for processing (1)

• src/main/java/com/iemr/common/data/email/StockAlertData.java (1 hunks)

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

• GitHub Check: style-check / checkstyle
• GitHub Check: Package-test
• GitHub Check: Analyze (java)
• GitHub Check: Build