Skip to content

Update SingleStore profile: tagline, RAG workload, agent use case, st… - #1

Merged
karthikdivi merged 1 commit into
onecompiler:mainfrom
rand4711:patch-1
Nov 12, 2026
Merged

karthikdivi merged 1 commit into
onecompiler:mainfrom
rand4711:patch-1

Conversation

@rand4711

Copy link
Copy Markdown
Contributor

What changed and why

Thanks for opening the repo for PRs. This changes databases/singlestore.json only. I work at SingleStore, so the box below is ticked.

  • tagline: "Distributed SQL running transactions, analytics, vector and full-text search in one engine on live data." It now covers the workloads the profile already lists (104 chars).
  • workloads: added rag. Full-text and vector search run in one SQL query with reranking.
  • strengths: added "MCP server and SQL AI functions let AI agents query and act on live data."
  • weaknesses: "Rowstore tables require data to fit in memory" became "Optional in-memory rowstore tables must fit in RAM; the default columnstore lives on local disk and tiers to object storage." The trade-off stays. The new text says which table type it covers, because columnstore is the default.
  • useCases: "Replacing a MySQL + Elasticsearch + warehouse combination" became "Apps and AI agents that read and write live business data".
  • tags: added rag.
  • lastVerified: 2026-11-10.

Nothing else changed. The weaknesses on licensing, missing triggers and materialized views, and shard keys are all still there.

Sources (also added to the profile's sources)

@karthikdivi
karthikdivi merged commit 7352d41 into onecompiler:main Nov 12, 2026
1 check passed
@karthikdivi

Copy link
Copy Markdown
Member

@rand4711 We have merged the PR. The changes will reflect within a day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants