Skip to content

Commit 9160343

Browse files
Update components.mdx
1 parent 451611a commit 9160343

File tree

1 file changed

+14
-39
lines changed

1 file changed

+14
-39
lines changed

docs-v2/pages/connect/components.mdx

Lines changed: 14 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1032,6 +1032,10 @@ This prop type is used by these database actions:
10321032
- `azure_sql-execute-raw-query`
10331033
- `turso-execute-query`
10341034

1035+
<Callout type="warning">
1036+
The `sql` prop is only supported in the Pipedream server SDK and REST API, and is not currently supported in `connect-react`.
1037+
</Callout>
1038+
10351039
#### Configuration
10361040

10371041
When configuring these actions, you'll need to provide:
@@ -1042,7 +1046,7 @@ When configuring these actions, you'll need to provide:
10421046
```javascript
10431047
const configuredProps = {
10441048
postgresql: {
1045-
authProvisionId: "apn_xxxxxxx""
1049+
authProvisionId: "apn_xxxxxxx"
10461050
},
10471051
sql: {
10481052
auth: {
@@ -1061,11 +1065,12 @@ You can use prepared statements by including placeholders in your query and prov
10611065
- **PostgreSQL** uses `$1`, `$2`, `$3`, etc. for numbered parameters
10621066
- **Snowflake**, **MySQL, Azure SQL, Microsoft SQL Server, and Turso** use `?` for positional parameters
10631067

1064-
**PostgreSQL Example:**
1068+
<Tabs items={['PostgreSQL example', 'MySQL example']}>
1069+
<Tabs.Tab>
10651070
```javascript
10661071
const configuredProps = {
10671072
postgresql: {
1068-
authProvisionId: process.env.ACCOUNT_ID
1073+
authProvisionId: "apn_xxxxxxx"
10691074
},
10701075
sql: {
10711076
auth: {
@@ -1076,12 +1081,12 @@ const configuredProps = {
10761081
}
10771082
}
10781083
```
1079-
1080-
**MySQL Example:**
1084+
</Tabs.Tab>
1085+
<Tabs.Tab>
10811086
```javascript
10821087
const configuredProps = {
10831088
mysql: {
1084-
authProvisionId: process.env.ACCOUNT_ID
1089+
authProvisionId: "apn_xxxxxxx"
10851090
},
10861091
sql: {
10871092
auth: {
@@ -1092,6 +1097,9 @@ const configuredProps = {
10921097
}
10931098
}
10941099
```
1100+
</Tabs.Tab>
1101+
</Tabs>
1102+
10951103

10961104
<Callout type="info">
10971105
Using prepared statements helps prevent SQL injection attacks by separating the SQL command structure from the data values being used, and is strongly recommended.
@@ -1167,39 +1175,6 @@ The response includes a `context.dbInfo` object containing detailed schema infor
11671175
"columnDefault": "CURRENT_TIMESTAMP"
11681176
}
11691177
}
1170-
},
1171-
"orders": {
1172-
"metadata": {},
1173-
"schema": {
1174-
"id": {
1175-
"tableName": "orders",
1176-
"columnName": "id",
1177-
"isNullable": "NO",
1178-
"dataType": "integer",
1179-
"columnDefault": "nextval('orders_id_seq'::regclass)"
1180-
},
1181-
"user_id": {
1182-
"tableName": "orders",
1183-
"columnName": "user_id",
1184-
"isNullable": "NO",
1185-
"dataType": "integer",
1186-
"columnDefault": null
1187-
},
1188-
"total": {
1189-
"tableName": "orders",
1190-
"columnName": "total",
1191-
"isNullable": "NO",
1192-
"dataType": "numeric",
1193-
"columnDefault": null
1194-
},
1195-
"created_at": {
1196-
"tableName": "orders",
1197-
"columnName": "created_at",
1198-
"isNullable": "YES",
1199-
"dataType": "timestamp with time zone",
1200-
"columnDefault": "CURRENT_TIMESTAMP"
1201-
}
1202-
}
12031178
}
12041179
}
12051180
}

0 commit comments

Comments
 (0)