1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-31 11:38:11 +00:00
serenity/Tests/LibSQL
Timothy Flynn 2397836f8e LibSQL+SQLServer: Introduce and use ResultOr<ValueType>
The result of a SQL statement execution is either:
    1. An error.
    2. The list of rows inserted, deleted, selected, etc.

(2) is currently represented by a combination of the Result class and
the ResultSet list it holds. This worked okay, but issues start to
arise when trying to use Result in non-statement contexts (for example,
when introducing Result to SQL expression execution).

What we really need is for Result to be a thin wrapper that represents
both (1) and (2), and to not have any explicit members like a ResultSet.
So this commit removes ResultSet from Result, and introduces ResultOr,
which is just an alias for AK::ErrorOrr. Statement execution now returns
ResultOr<ResultSet> instead of Result. This further opens the door for
expression execution to return ResultOr<Value> in the future.

Lastly, this moves some other context held by Result over to ResultSet.
This includes the row count (which is really just the size of ResultSet)
and the command for which the result is for.
2022-02-10 23:11:13 +01:00
..
CMakeLists.txt Tests: Remove all file(GLOB) from CMakeLists in Tests 2021-09-02 09:08:23 +02:00
TestSqlBtreeIndex.cpp LibSQL: Improve error handling 2021-12-04 20:49:22 +03:30
TestSqlDatabase.cpp Tests: Cast unused smart-pointer return values to void 2021-12-05 15:31:03 +01:00
TestSqlExpressionParser.cpp Everywhere: Update copyrights with my new serenityos.org e-mail :^) 2022-01-31 18:23:22 +00:00
TestSqlHashIndex.cpp LibSQL: Improve error handling 2021-12-04 20:49:22 +03:30
TestSqlStatementExecution.cpp LibSQL+SQLServer: Introduce and use ResultOr<ValueType> 2022-02-10 23:11:13 +01:00
TestSqlStatementParser.cpp LibSQL: Implement DESCRIBE TABLE tests 2022-02-05 00:35:03 +01:00
TestSqlValueAndTuple.cpp LibSQL: Add 'schema' and 'table' to TupleElementDescriptor 2021-11-10 14:47:49 +01:00