Skip to content

Commit e1911d4

Browse files
committed
docs: Add a note on placeholders in a generated query
1 parent 04deee9 commit e1911d4

File tree

2 files changed

+14
-0
lines changed

2 files changed

+14
-0
lines changed

docs/pages/product/workspace/playground.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,13 @@ on the <Btn>Generated SQL</Btn> tab. Click <Btn>Copy</Btn> to put it into your c
156156
src="https://ucarecdn.com/d2b6e514-9219-49ea-bae6-bcd0f1936542/"
157157
/>
158158

159+
<InfoBox>
160+
161+
Note that a generated query can contain placeholders, e.g., `?` or `$1`, for parameters
162+
that Cube passes to an underlying data source driver later when executing the query.
163+
164+
</InfoBox>
165+
159166
## Copying API queries
160167

161168
View the queries for respective data APIs on the <Btn>SQL API</Btn>, <Btn>REST API</Btn>,

docs/pages/reference/rest-api.mdx

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,13 @@ Example response:
145145
}
146146
```
147147

148+
<InfoBox>
149+
150+
Note that a generated query can contain placeholders, e.g., `?` or `$1`, for parameters
151+
that Cube passes to an underlying data source driver later when executing the query.
152+
153+
</InfoBox>
154+
148155
## `/v1/meta`
149156

150157
Get meta-information for cubes and views defined in the data model. Information about cubes and views with `public: false` will not be returned.

0 commit comments

Comments
 (0)