@@ -15,7 +15,7 @@ This example illustrates the main ones.
15
15
All the examples will implement the same simple form:
16
16
a form that asks for a person's name, email, and age.
17
17
18
- ## Storing the state in the database
18
+ ## [ Storing the state in the database] ( ./database/ )
19
19
20
20
You can store the state of the partially filled form in the database,
21
21
either in the final table where you want to store the data,
@@ -30,7 +30,7 @@ allowing you to have more relaxed column constraints in the partially filled dat
30
30
- the website administrator needs to manage a dedicated table for the form state
31
31
- old partially filled forms may pile up in the database
32
32
33
- ## Storing the state in cookies
33
+ ## [ Storing the state in cookies] ( ./cookies/ )
34
34
35
35
You can store each answer of the user in a cookie,
36
36
using the
@@ -48,7 +48,7 @@ and retrieve it on the next step using the
48
48
- the user needs to have cookies enabled to fill in the form
49
49
- if the user leaves the form before submitting it, the form state will keep being sent to all the pages he visits until he submits the form.
50
50
51
- ## Storing the state in hidden fields
51
+ ## [ Storing the state in hidden fields] ( ./hidden/ )
52
52
53
53
You can store the state of the partially filled form in hidden fields,
54
54
using ` 'hidden' as type ` in the [ form component] ( https://sql.datapage.app/component.sql?component=form#component ) .
0 commit comments