Fix TestParseExecuteData in mysql_protocol_test.go

[forsaken628]

What type of PR is this?

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

Which issue(s) this PR fixes:

issue #15125

What this PR does / why we need it:

fix test

[matrix-meow]

@forsaken628 Thanks for your contributions!

Pull Request Review:

Title:

The title of the pull request is clear and specific, indicating that the purpose of the PR is to fix an issue related to the test TestParseExecuteData in mysql_protocol_test.go.

Body:

The body of the pull request provides information about the type of PR (Test and CI), the related issue (#15125), and a brief description stating that the PR is fixing a test. It would be beneficial to include more details about the specific problem being addressed in the test and the changes made to resolve it.

Changes:

1. Removed Unused Import:

   • The import statement for github.com/matrixorigin/matrixone/pkg/container/vector has been removed from the file mysql_protocol_test.go. This change is good as it eliminates unused code and improves code cleanliness.

2. Code Removal:

   • The params initialization using vector.NewVec(types.T_varchar.ToType()) has been removed from the FuzzParseExecuteData function. This change seems to be related to the test being fixed.
   • Similarly, the params initialization has been removed from the TestParseExecuteData function. This change aligns with the previous removal and may be part of the fix.

3. Comment Removal:

   • A commented block of code related to a FIXME and refactoring has been removed. This cleanup is acceptable if the code is no longer relevant.

Suggestions for Improvement:

1. Detailed Description:

   • Provide a more detailed description in the body of the pull request explaining the specific issue with the TestParseExecuteData test and how the changes address it. This will help reviewers and future developers understand the context better.

2. Security Consideration:

   • Ensure that the removal of the params initialization does not introduce any security vulnerabilities or impact the functionality of the tests. Verify that the removal is intentional and does not affect the test's correctness.

3. Code Cleanup:

   • Consider performing a thorough code review to identify and remove any other unused code, comments, or redundant pieces of code in the file while maintaining code readability and consistency.

4. Testing:

   • Verify that the changes made in the test functions (FuzzParseExecuteData and TestParseExecuteData) do not cause any regressions and that the tests still cover the intended functionality adequately.

5. Documentation Update:

   • If the removal of the commented block is no longer relevant, consider updating the surrounding documentation or adding a new comment to explain the reason for its removal.

By addressing the suggestions and ensuring the changes do not introduce any new issues, the pull request can be optimized for better code quality and maintainability.