You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/official-site/sqlpage/migrations/01_documentation.sql
+17-3Lines changed: 17 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -233,9 +233,23 @@ INSERT INTO parameter(component, name, description, type, top_level, optional) S
233
233
INSERT INTO example(component, description, properties) VALUES
234
234
(
235
235
'form',
236
-
'A form that asks the user for a parameter named "component", and then posts the results to another page named "documentation.sql".
237
-
That file could contain a sql statement like "SELECT * FROM documentation WHERE component_name = $component" to display the documentation for the component the user selected.
238
-
Or it could contain a sql statement like "INSERT INTO components(name) VALUES ($component)" to allow users to create a new component.',
236
+
'
237
+
A form that asks the user for a parameter named `component`, and then posts the results to another page named `documentation.sql`.
238
+
That file could contain a sql statement like
239
+
```sql
240
+
SELECT * FROM documentation WHERE component_name = $component
241
+
```
242
+
to display the documentation for the component the user selected.
243
+
244
+
Or it could contain a sql statement like
245
+
```sql
246
+
INSERT INTO components(name) VALUES ($component)
247
+
```
248
+
249
+
to allow users to create a new component.
250
+
251
+
When loading the page, the value for `$component` will be `NULL` if no value has been submitted.
0 commit comments