distributed-database

Is your feature request related to a problem? Please describe.

I'm using CockroachDB CCL v21.1.11 (x86_64-unknown-linux-gnu, built 2021/10/18 14:39:35, go1.15.14)

Consider this table:

create table t (n decimal(3));

The numeric precision is produced correctly in information_schema.columns.numeric_precision:

select numeric_precision from information_schema

Calling setclass in fdbcli will try to change any process that matches the process filter given. If no processes are found, it silently does nothing. Instead, it should report back to the user that no processes matched the given filter.

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

There are multiple issues with the individual beta feature flags. I believe the core issue is lack of understanding of parser_ybc_beta_feature. See the definition:

#define parser_ybc_beta_feature(pos, feature, has_own_flag) \
    check_beta_feature(pos, yyscanner, has_own_flag ? "FLAGS_ysql_beta_feature_" feature : NULL, feature)

If has_own_flag is true, there should be a c

With Hive connector

trino:default> CREATE TABLE one (a varchar);
            -> CREATE VIEW two AS SELECT * FROM one;
CREATE TABLE
CREATE VIEW

DROP TABLE is rejected on a view:

trino:default> DROP TABLE two;
Query 20210906_150832_00015_id3y3 failed: line 1:1: Table 'hive.default.two' does not exist, but a view with that name exists. Did you mean DROP VIEW hive.default.t

Required by DataGrip. See crate/crate#11726

The full query is

select L.transactionid::varchar::bigint as transaction_id
from pg_catalog.pg_locks L                                                                               
where L.transactionid is not null                                                                        
order by pg_catalog.age(L

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)

Currently a cache node object consists of a Key, a Value and a TTL. We should also add a field specifying the type of the Value