add issue 16178 cases

[heni02]

User description

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #16178

What this PR does / why we need it:

add issue 16178 cases

---

PR Type

Tests

---

Description

• Added new test cases for issue [Bug]: Batch insert fails #16178.
• Created storage table with columns collecttime, value, account, and interval.
• Inserted multiple rows into storage table using prepared statements.
• Selected and verified data from storage table to ensure correctness.

---

Changes walkthrough 📝

Relevant files

Tests

prepare.result Add test case for `storage` table with prepared statements test/distributed/cases/prepare/prepare.result Added new test case for storage table creation. Inserted multiple rows into storage table using prepared statements. Selected and verified data from storage table. +47/-0    prepare.test Add test case for `storage` table with prepared statements test/distributed/cases/prepare/prepare.test Added new test case for storage table creation. Inserted multiple rows into storage table using prepared statements. Selected and verified data from storage table. +40/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the PR primarily involves adding new test cases and SQL statements for database operations. The changes are straightforward and localized to specific test files, making the review process relatively simple.
🧪 Relevant tests	Yes
⚡ Possible issues	No
🔒 Security concerns	No

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Add a check to ensure the table does not already exist before creating it Consider adding a check to ensure the table storage does not already exist before creating it. This will prevent potential errors if the script is run multiple times. test/distributed/cases/prepare/prepare.result [432-438] -CREATE TABLE `storage` ( +CREATE TABLE IF NOT EXISTS `storage` ( `collecttime` DATETIME NOT NULL, `value` DOUBLE NOT NULL, `account` VARCHAR(128) NOT NULL, `interval` INT NOT NULL, PRIMARY KEY (`collecttime`,`account`) ); Suggestion importance[1-10]: 8 Why: Adding a check for the existence of the table before creating it is a good practice to prevent errors in scripts that might be run multiple times. This suggestion correctly identifies a potential improvement in the SQL script to enhance robustness.	8
Data integrity	Add constraints to enforce valid ranges for value and interval columns To ensure data integrity, consider adding constraints to the value and interval columns to enforce valid ranges. test/distributed/cases/prepare/prepare.result [434-436] -`value` DOUBLE NOT NULL, +`value` DOUBLE NOT NULL CHECK (`value` >= 0), `account` VARCHAR(128) NOT NULL, -`interval` INT NOT NULL, +`interval` INT NOT NULL CHECK (`interval` > 0), Suggestion importance[1-10]: 7 Why: Adding constraints to ensure data integrity is a valuable suggestion. It enhances the reliability of the database by preventing invalid data entries. The suggestion correctly targets the new columns added in the PR and proposes a practical improvement.	7