ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
MySQL composite indexes follow the leftmost-prefix rule: a query must reference a contiguous prefix of index columns starting from the first. This guide explains column ordering, covering indexes, verification with EXPLAIN, and common mistakes that waste write throughput.
Learn how to add a Phoenix secondary index to an HBase table, verify that the planner uses it, and weigh the read‑speed gains against write‑amplification and storage costs.
Create a Phoenix secondary index on a non‑key column to replace full HBase scans with index scans, cutting query latency. Covers prerequisites, DDL syntax, build monitoring, plan verification, and rollback steps.
When most of your rows are filtered out by a common predicate, a partial index can cut index size and write overhead. Learn how to create, test, and trade-off partial indexes in PostgreSQL.
Learn how to pick a ClickHouse MergeTree primary key that enables partition pruning and skip indexes, turning slow range scans into fast lookups.
Guide to decide between Couchbase FTS and N1QL LIKE/REGEXP for text queries, with a compact trade‑off table, step‑by‑step index creation, query validation, and rollback steps.
Learn how to use PostgreSQL partial indexes to reduce storage and write overhead by indexing only a specific subset of rows using a WHERE predicate.
Cypher's variable-length path patterns answer 'what's connected within N hops' in one line — but the hop bound and relationship-type filter are what stand between a fast query and a full-graph scan.
Automatic indexing in Azure Cosmos DB for NoSQL indexes every property on write, simplifying schema evolution but consuming request units per operation. When a custom indexing policy excludes specific paths, the default composite index interaction with remaining fields becomes a design consideration, particularly for range and equality queries. The policy ch
clickhouse
couchbase