Persistent field not there (#6)

Not sure if this was a previous version of Quarkus, but the `persistent` field is no longer there.
This commit is contained in:
Eric Deandrea
2019-11-15 05:30:57 -05:00
committed by James Falkner
parent 076f6e1b09
commit ec8882bb74

View File

@@ -214,7 +214,7 @@ We call the endpoint with `curl` then send the output through `jq` to make the o
]
----
It's working! Note that the `id` and `persistent` fields were added to our entity, but never appear in our query APIs and can be safely ignored most of the time.
It's working! Note that the `id` field was added to our entity, but never appear in our query APIs and can be safely ignored most of the time.
[NOTE]
====
@@ -293,7 +293,6 @@ You should only see **one** person with BLUE eyes:
----
[
{
"persistent": true,
"id": 1,
"birth": "1974-08-15",
"eyes": "BLUE",
@@ -315,14 +314,12 @@ You should see **two** people born in 1990 or earlier:
----
[
{
"persistent": true,
"id": 1,
"birth": "1974-08-15",
"eyes": "BLUE",
"name": "Farid Ulyanov"
},
{
"persistent": true,
"id": 2,
"birth": "1984-05-24",
"eyes": "BROWN",
@@ -447,7 +444,6 @@ This should return a single entity (since in our 3-person sample data, only one
{
"data": [
{
"persistent": true,
"id": 1,
"birth": "1974-08-15",
"eyes": "BLUE",
@@ -606,4 +602,4 @@ Skip around a few pages, try some different searches, and notice that the data i
== Congratulations
In this exercise you got a glimpse of the power of Quarkus apps when dealing with large amounts of data. There is much more to Quarkus than fast startup times and low resource usage, so keep going!
In this exercise you got a glimpse of the power of Quarkus apps when dealing with large amounts of data. There is much more to Quarkus than fast startup times and low resource usage, so keep going!