Skip to main content

Tutorial: Save data to a Datastore

In the last section, we made a HTTP request that created a 404. We'll use the trace of that HTTP request to build an endpoint, a technique we call Trace Driven Development.

  1. Go to the 404 section of the sidebar and you should see the HTTP request that you just made with your REPL.

  2. Hit the plus (+) button next to the 404. This creates a HTTP endpoint with the HTTP method (POST) and path (/test) set from the request that creates the 404.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.44.54_AM.png

  1. Hover over the white dot on the left hand side. Here, you can see the full body of the incoming trace from when you posted to the endpoint from the REPL, including the body.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.45.57_AM.png

  1. Let's save the request body to a variable by typing let data = request.body. The autocomplete knows the field names of request from the trace, and will complete them for you.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.47.10_AM.png

  1. Let's put this in a datastore. Type "DB" to bring up a list of Dark datastore functions.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.48.24_AM.png

In this case, we want DB::set, which takes three arguments.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.48.51_AM.png

  1. Now let's make our datastore. Press Ctrl-k/Cmd-k to bring up the omnibox, and create a new datastore called "Requests", with fields data and time.

img/gettingstarted/datastore.png

  1. Now that we have a datastore, let's finish our post endpoint.

    The first argument is the record we're inserting. This needs to match the schema, and so it needs to include both date and time (you cannot insert records that are missing fields). Insert our data from above (seeing the live value to the left) and use the Date::now function to get the time field.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.57.58_AM.png

  1. We need a unique key for each record that we store. The DB::generateKey function generates random keys this is useful when your record has no obvious unique identifier.

img/gettingstarted/Screen_Shot_2020-02-11_at_10.59.24_AM.png

  1. The final argument is the Datastore: Requests.

img/gettingstarted/Screen_Shot_2020-02-11_at_11.00.04_AM.png

  1. To call the DB::set function, we first need to run the two functions with side effects (DB::generateKey and Date::now) by hitting the play button. After hitting those two play buttons, the DB::set play button will be enabled:

img/gettingstarted/Screen_Shot_2020-02-11_at_11.00.55_AM.png

  1. Finally, hitting the play button for DB::set inserts the record into the datastore. This locks the datastore, preventing us from changing the schema, which we see indicated by the red lock (🔒) icon.

img/gettingstarted/Screen_Shot_2020-02-11_at_11.01.32_AM.png

Congratulations! You've created a Dark Datastore and stored data inside it.