distributed-database

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

Describe the problem

To use a timestamp value in decimal, in Postgres, I use the to_timestamp() function as follows

select to_timestamp(1646906263.278);

Since cockroach doesn't have to_timestamp(), I use a cast instead:

select 1646906263.278::timestamptz;

But it results in SQL Error [42846]: ERROR: invalid cast: decimal -> timestamptz

Casting an inte

Hi community,

This issue is for OpenForce

Our CMake build process produces tarball packages using the cpack TGZ target. This produces a server and client package with a file layout meant to match where the various artifacts go.

Meanwhile, the packages we include on the download page are a flat archive of various binaries produced by the build process. This include one regular package and one debug package with debug symbols for a few

Description

Currently, the table "write_read_test" in keySpace "system_platform" is counted towards user tables, so even when the user has only one table, the portal shows the user has two tables.

![image](https://user-images.githubusercontent.com/23063104/152056332-f32dc60a-d9ce-

Need to migrate trino-maven-plugin to use GitHub actions instead of Travis CI. See trinodb/trino#6859 for some guidance.

Use case:
Postgres compatible tools like Datagrip, DBeaver, etc. want to get (and sometimes set e.g. Azure Data Studio) the datestyle used by the database. It seems like there is already some implementation for that.

Feature description:
As a db tool engineer I want to be able to fetch the set datestyle of a database to be know how to interpret dates in my tool.

extra: ability

I thought the size of std::bitset<16> is 2 bytes, but it turns out it's 8 bytes

#include <bitset>
#include <iostram>

int main() {
    std::cout << sizeof(std::bitset<2>) << std::endl;
    std::cout << sizeof(std::bitset<8>) << std::endl;
    std::cout << sizeof(std::bitset<16>) << std::endl;
    std::cout << sizeof(std::bitset<32>) << std::endl;
    std::cout << sizeof(std::bitset

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