1
89%
master: 88%

Ran 05 Oct 2023 03:08PM UTC

Files 60

Run time 1s

Badge

Embed ▾

Committed 05 Oct 2023 02:53PM UTC coverage: 89.543% (+0.03%) from 89.518%

Job # 6420757008.1

Build Type

Pull #382

github

Committed by

DifferentialOrange

Commit Message

api: return error if no tuples/objects

Before this patch, the behavior of `*_many` requests if empty array of
tuples/objects were rather confusing. For example, due to format
processing all `*_object_many` operations resulted in `nil, {}` --
error request with zero errors. `insert_many` and `replace_many` calls
result in `nil, nil` -- no result, no error. `upsert_many` results in
`{metadata = metadata}, nil` with no `rows` in response. Thus, for all
six `*_many` calls trying to execute the request with empty array on
input result in malformed response.

After this patch, trying to run `*_many` request with empty array of
tuples/objects will result in `nil, {err}`, similar to existing
`*_many` API. Single tuple crud API already does not allow to run with
no tuples/objects.

Closes #377

Pull Request Pull Request #382: api: return error if no tuples/objects

Run Details

4641 of 5183 relevant lines covered (89.54%)

16852.16 hits per line

tarantool / crud / 6420757008 / 1
89%
master: 88%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6420757008.1

tarantool / crud / 6420757008 / 1 89% master: 88%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6420757008.1

tarantool / crud / 6420757008 / 1
89%
master: 88%

README BADGES
x