This commit fixes that non-admin users can't read queries from the query cache.
An attempt to read from the cache used to result in the following error:
sbroad error: failed to get space_def: box error: AccessDenied: Read access to space '_pico_table' is denied for user 'alex3'

Previously, an error would occur when a user ran the same query twice.
During the first execution, the query was prepared and cached. However,
on the second execution, the client attempted to retrieve the query from the
cache and encountered an access denied error.

- we didn't check that index name is unique
in indexes meta table. That led to panics
when index with same name was created for
two tables.
- previous commit set wrong sbroad submodule.
Set sbroad submodule to correct commit

Dmitry Ivanov authored 10 months ago and Maksim Kaitmazian committed 10 months ago

By default, tarantool submodule is built and linked against its bundled
version of openssl (1.1.1q). This causes issues when we try to link
against the host system's shared openssl of a different version (e.g. 3.0):

```
= note: /usr/bin/ld: target/debug/build/tarantool-sys/static/tarantool-prefix/src/tarantool-build/src/lib/crypto/libtcrypto.a(crypto.c.o): in function `crypto_stream_begin':
          tarantool-sys/src/lib/crypto/crypto.c:154:(.text+0x841): undefined reference to `EVP_CIPHER_key_length'
          /usr/bin/ld: tarantool-sys/src/lib/crypto/crypto.c:160:(.text+0x852): undefined reference to `EVP_CIPHER_iv_length'
```

Thus, we should pass `-DENABLE_BUNDLED_OPENSSL=OFF` to properly
configure tarantool and prevent missing symbols from occurring.

Maksim Kaitmazian authored 1 year ago and Maksim Kaitmazian committed 10 months ago

This commit adds supportion of extended query messages and
error handling in extended query pipeline.

Features that are not implemented:
 * binary encoding
 * parameterized queries

Maksim Kaitmazian authored 1 year ago and Maksim Kaitmazian committed 10 months ago

Closes TODO: check if coio wrapper returns 0 or EOF error.

Dmitry Ivanov authored 1 year ago and Maksim Kaitmazian committed 10 months ago

Previously, we'd loop forever if there wasn't enough data for decode.

Maksim Kaitmazian authored 1 year ago and Maksim Kaitmazian committed 10 months ago

If ibuff is not empty we should read messages from the buffer.
Reading messages when the buffer is not empty may lead to deadlock,
for instance, if the frontend send a series of queries and waits backend
response to send other messages, while backend tries to read new
messages.