Why doesn't Convex have SELECT or COUNT?

Convex is a backend platform that, unlike traditional databases such as Postgres, does not support direct SELECT or COUNT operations due to its design as both a relational and document database. This design choice is rooted in Convex's philosophy of avoiding "pretend-cheap primitives" and instead emphasizing explicit modeling to ensure consistent performance and pricing. Convex's queries are automatically cached, avoiding repeated database reads and thus potentially reducing costs. However, its approach requires users to model data explicitly, such as separating large values into different tables and manually maintaining counts to optimize performance and resource usage. While Convex could theoretically implement SELECT and COUNT, these features might mask real costs and lead to unpredictable performance due to the platform's unique handling of data storage and retrieval. For developers, this means embracing Convex's distinct approach to data modeling and leveraging tools like the Convex Aggregate Component for complex operations like counting or summing data.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.