"found" by the @discordapp troops the hard way: https://status.discordapp.com/incidents/62gt9cgjwdgf
pinging @zorkian who pointed it out to me.

trivial to repro, this is against a 3.3.13 on fedora-31.

$ etcdctl set /baa schnorp
$ etcdctl get /baa
schnorp
$ echo -ne 'PUT /v2/keys/baa HTTP/1.1\r\nHost: boo\r\nContent-Length: 123\r\n\r\n' | nc localhost 2379
HTTP/1.1 200 OK
...
$ et

In postgres:

rafiss@127:postgres> create table example (a "char");
CREATE TABLE

rafiss@127:postgres> insert into example values ('abc');
INSERT 0 1

rafiss@127:postgres> select a from example;
+-----+
| a   |
|-----|
| a   |
+-----+
SELECT 1

In cockroachdb

root@:26257/defaultdb> create table example (a "char");
CREATE TABLE

root@:26257/defaultdb>  insert into

Refactor OptimizeContextFactory.initProperties(final DatabaseType databaseType) method

        // TODO Logic could be improved.
        if (databaseType instanceof MySQLDatabaseType || databaseType == null) {
            properties.setProperty(LEX_CAMEL_NAME, Lex.MYSQL.name());
            properties.setProperty(CONFORMANCE_CAMEL_NAME, SqlConformanceEnum.MYSQL_5.name());
          

fdbcli flags currently contain a mixture of _ and - (probably for historic reasons). I would propose to unify the flags and only use either _ or - personally I tend to hyphens like recommended in the POSXI standard (https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html). Current fdbcli help output:

FoundationDB CLI 6.2 (v6.2.29)
usage: /usr/bin/fdb/6.2/fdbcli

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-

We already have a yb-ts-cli compact_tablet, but that works strictly on the TS side. We should be able to add a similar RPC on the master side, reusing the same logic of triggering the respective tablet/rocksdbs to flush.

When you change a query state filter e.g. showing 'Finished' queries or 'User Error' queries, the Show Limit is not respected immediately resulting in all queries being rendered. If a re-order interval is set then Show Limit is applied on the next query refresh. If there are a large number of queries in the history this can result in the browser crashing on the first render.

The following two c

Use case:
Right now one can only use date_trunc() to easily define time buckets. date_trunc() only supports predefine time intervals like 1 minute, 1 hour, etc. . In time-series use cases it is often necessary to define different time bucket sizes like e.g. '5 minutes' or '20 minutes'

a workaround for this is the - error prone - integer division on the timestamp e.g.

S

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

日期转换函数timpstamp插入和保存都是int64，后面是否会支持yyyy-MM-dd HH:mm:ss这种形式，同时支持内部日期函数转换，将int64转换成yyyy-MM-dd HH:mm:ss。对于int64，现在的解决措施只能是应用内转换和新建string字段展示正常的日期格式