modify snapshot case syntax(1.2-dev)

[Ariznawlll]

What type of PR is this?

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

Which issue(s) this PR fixes:

issue ##16180

What this PR does / why we need it:

modify snapshot case syntax(1.2-dev)

[matrix-meow]

@Ariznawlll Thanks for your contributions!

Pull Request Review:

Title:

The title of the pull request is clear and concise, indicating that the snapshot case syntax is being modified for version 1.2-dev.

Body:

The body of the pull request provides information about the type of PR, the related issue, and a brief description of the changes made. It would be helpful to have more detailed information about why this modification is necessary for better context.

Changes:

1. In the sys_restore_to_nonsys_account.sql file, multiple instances of the restore command syntax are being modified. The changes involve removing the duplicate account name after the from snapshot keyword in some cases.

Feedback and Suggestions for Improvement:

1. Redundant Account Name in Restore Command:

   • The changes in the restore commands where the account name is repeated after the from snapshot keyword seem redundant. For example:
     • Before: restore account acc01 from snapshot sp01 to account acc01;
     • After: restore account acc01 from snapshot sp01;
   • Suggestion: Remove the duplicate account name after the from snapshot keyword to simplify the syntax and avoid redundancy.

2. Consistency in Syntax:

   • Ensure consistency in the syntax of the restore commands throughout the file. Some commands have the account name repeated, while others do not.
   • Suggestion: Review all instances of restore commands and ensure they follow a consistent syntax pattern for clarity and maintainability.

3. Documentation and Context:

   • Provide more detailed information in the pull request description about why these modifications are necessary. Understanding the rationale behind the changes can help reviewers and future developers.
   • Suggestion: Add a more descriptive explanation in the pull request body to clarify the purpose of modifying the snapshot case syntax.

4. Security Considerations:

   • Ensure that the modifications do not introduce any security vulnerabilities, especially when dealing with account and snapshot management.
   • Suggestion: Conduct a security review to verify that the changes do not compromise the system's security.

5. Optimization:

   • Consider optimizing the restore commands for better performance or readability if possible.
   • Suggestion: Evaluate if there are any additional optimizations that can be made to enhance the efficiency of the restore commands.

By addressing the issues mentioned above and considering the suggestions provided, the pull request can be improved in terms of clarity, consistency, and potential optimizations.