Support replace and upsert operations

[savolgin]

Issue #7

[olegrok]

Thanks for your patch, please drop the first commit (Support tuples as result type) from current pull request, it's not related to "Support replace and upsert operations"

[dokshina]

Thanks a lot!

Please, alseo describe new operations in README.

[savolgin]

Please, alseo describe new operations in README.

redme updated

Thanks for your patch, please drop the first commit (Support tuples as result type) from current pull request, it's not related to "Support replace and upsert operations"

dropped

[olegrok]

I suggest you to add tests for both engines - memtx and vinyl.

See example - #4

[olegrok]

See my last comment. After fixing it - LGTM

[olegrok]

LGTM. Seems you need to update changelog as well

[savolgin]

Change log updated

[dokshina]

a nit: since we already have system_fields conception, maybe it can be

function utils.flatten(object, space_format, system_values)
    system_values = system_values or {}
    ...
    if system_values.bucket_id ~= nil and field_format.name == 'bucket_id' then ...
    -- if sometimes we have more system fields, it can be done in a cycle
    ...
end

[dokshina]

Thanks a lot for your patch!

Only one: please wait for new CI based on GitHub Actions is merged and rebase on it.
Then, it will be merged.