citusdata / citusdata/citus_docs

Add general SQL workaround involving CTEs

Open
#753 1 comment 0 reactions 0 assignees View on GitHub
blocked SE
Dominant language
CSS
Stars
58
Forks
60
PR merge metrics
No merged PRs in 30d

Description

## Why are we implementing it? (sales eng)

### What are the typical use cases?

Complex subqueries that Citus refuses to run.

## Communication goals (e.g. detailed howto vs orientation)

Explain how rewriting certain subqueries as CTEs is a workaround for complex subqueries.

TODO: Sai will provide examples of queries that don't work, and their rewritten forms that do.

### Good locations for content in docs structure

http://docs.citusdata.com/en/v7.5/develop/reference_workarounds.html

## How does this work? (devs)

### Example sql

### Corner cases, gotchas

### Are there relevant blog posts or outside documentation about the concept/feature?

### Link to relevant commits and regression tests if applicable

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.