Database

A database is a structured set of data held in a computer, most often a server. Databases use a database management system (DBMS) that interacts with users, similar to a lookup table. Modern databases are designed to allow for creation, querying, updating, and administration of the data it holds.

Today, etcdctl endpoint health only performs a quorum GET. If server is corrupted or exceeded quota (which put the server into read only mode), this command incorrectly returns healthy.

While I try to change header titles by passing array of titles to options like below it does not override the headers. Instead it writes new headers first and original data with old headers again from next cell.

I am experiencing the same problem.

In addition, sheets js is mutating the header array passed in, which is not something I would ever expect.

Example:

const head

SQL supports hidden columns: columns that are only included in a projection if explicitly requested. An example of this is the rowid column that is created on tables without explicitly primary keys.

Currently, there is no way to get a hidden column on a user-defined table: it's only possible if you manually set the hidden boolean in the table descriptor, by editing the CockroachDB source code

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Issue description

Go 1.15 will introduce a new Validator interface, which may be implemented by Conn to allow drivers to signal if a connection is valid or if it should be discarded:

https://tip.golang.org/pkg/database/sql/driver/#Validator

@valu

Today, we translate this as @value IS NULL OR LTRIM(RTRIM(@value)) = N''. But I have a few questions:

Why do we trim both the start and the end? Just one would produce the same result with less processing.
More importantly, why do we trim at all? As we know from our StartsWith research, N' ' = N'' returns true in SQL Server.

IMHO, the translation should be `@value IS NULL OR @valu

Like what was done in #943, it would be good if searchable attributes were also sorted in lexicographical order.

Sep	OCT	Nov
	13
2019	2020	2021

Database

Here are 14,408 public repositories matching this topic...

etcd-io / etcd

pingcap / tidb

SheetJS / sheetjs

metabase / metabase

typeorm / typeorm

influxdata / influxdb

cockroachdb / cockroach

mongodb / mongo

sqlmapproject / sqlmap

prisma / prisma1

dbeaver / dbeaver

PostgREST / postgrest

huihut / interview

pubkey / rxdb

realm / realm-cocoa

dgraph-io / dgraph

typicode / lowdb

taosdata / TDengine

sqlitebrowser / sqlitebrowser

LeCoupa / awesome-cheatsheets

pouchdb / pouchdb

amark / gun

apache / shardingsphere

boltdb / bolt

realm / realm-java

arangodb / arangodb

go-sql-driver / mysql

Issue description

dotnet / efcore

valeriansaliou / sonic

meilisearch / MeiliSearch

Essential cookies

Always active

Analytics cookies