RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-31 13:48:12 +00:00
Code Issues Activity Actions

LibSQL+SQLServer: Introduce and use ResultOr<ValueType>

Browse source 
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.
This commit is contained in:
Timothy Flynn 2022-02-10 14:43:00 -05:00 • committed by Andreas Kling
parent 6409618413
commit 2397836f8e
15 changed files with 259 additions and 330 deletions
Download patch file Download diff file Expand all files Collapse all files

24
Userland/Libraries/LibSQL/Result.cpp
View file

@ -9,30 +9,6 @@
namespace SQL {
void Result::insert(Tuple const& row, Tuple const& sort_key)
{
if (!m_result_set.has_value())
m_result_set = ResultSet {};
m_result_set->insert_row(row, sort_key);
}
void Result::limit(size_t offset, size_t limit)
{
VERIFY(has_results());
if (offset > 0) {
if (offset > m_result_set->size()) {
m_result_set->clear();
return;
}
m_result_set->remove(0, offset);
}
if (m_result_set->size() > limit)
m_result_set->remove(limit, m_result_set->size() - limit);
}
String Result::error_string() const
{
VERIFY(is_error());