To set up unit testing for your SQL Script procedure, you use a library with language SQLSCRIPT TEST. A library with language SQLSCRIPT TEST is a special type of library that contains SQL Script test cases for testing the behavior and performance of SQL Script procedures. A SQL Script test case is a SQL Script procedure that has the prefix TEST_ and that uses the ASSERT and EXPECT statements to verify the expected results and outputs of the procedure under test. A library with language SQLSCRIPT TEST can be created in the SAP Web IDE for SAP HANA or in the SAP HANA Studio, and can be executed by using the SQL Script Test Framework, which is a tool that runs the test cases and generates a test report.

The following options are not used to set up unit testing for your SQL Script procedure, but for other purposes:

• SQL Script logging procedures: SQL Script logging procedures are procedures that use the APPLY_FILTER and APPLY_AGGREGATION statements to perform logging operations on table variables or cursors. SQL Script logging procedures can be used to monitor and analyze the execution of SQL Script procedures, but not to test their correctness or functionality.
• The SQL Script debugger: The SQL Script debugger is a tool that allows you to debug SQL Script procedures by setting breakpoints, inspecting variables, and stepping through the code. The SQL Script debugger can be used to identify and fix errors or bugs in SQL Script procedures, but not to verify their expected results or outputs.
• The SQL Script Code Analyzer: The SQL Script Code Analyzer is a tool that analyzes SQL Script code and provides suggestions and recommendations for improving its quality, performance, and maintainability. The SQL Script Code Analyzer can be used to optimize and refactor SQL Script code, but not to test its behavior or functionality.

References:

• [SAP HANA Platform Documentation], SAP HANA SQLScript Reference, Chapter 6: SQLScript Test Framework, pp. 153-158.
• [SAP HANA Platform Documentation], SAP HANA Developer Guide for SAP HANA XS Advanced Model, Chapter 7: Developing SQLScript Procedures, Section 7.4: Testing SQLScript Procedures, pp. 137-140.

 When a user is dropped with the “cascade” option, the user and all the objects owned by the user are deleted from the database. However, the objects that are owned by other users, or on which other users have privileges, are not affected by the drop command. The privileges granted to or by the dropped user are also revoked automatically. Therefore, the objects on which other users have privileges are not dropped, and the objects owned by other users are not dropped12.

The other options are not correct because they are not the consequences of dropping a user with the “cascade” option. The objects on which other users have privileges are not dropped, because they are not owned by the dropped user, and they may still be needed by the other users. The objects owned by other users are not dropped, because they are not related to the dropped user, and they may have dependencies or references to other objects. References:

• SAP HANA Platform, SAP HANA SQL and System Views Reference, SQL Reference Manual, SQL Statements, DROP USER
• SAP HANA Platform, SAP HANA Administration Guide, Security, User Management, Dropping Users

According to the SAP HANA Developer Guide, XSODATA supports the following HTTP commands to define the operations on the resources:

• DGET: Retrieves a single entity or a collection of entities from the data source.
• DPUT: Updates an existing entity in the data source.
• POST: Creates a new entity in the data source.
• DELETE: Deletes an existing entity from the data source.

The READ and INSERT commands are not valid HTTP commands for XSODATA. They are keywords that can be used in the service definition file (.xsodata) to specify the access mode for each entity set. References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111