From 78c811334c9e5477b86fd113fa2c4a261e167d15 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Wed, 17 Jun 2020 07:59:40 +0200 Subject: Refs #30190 -- Minor edits to JSONL serializer. Follow up to e29637681be07606674cdccb47d1e53acb930f5b. --- docs/topics/serialization.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/topics/serialization.txt b/docs/topics/serialization.txt index 7cc4905da3..9ef851368a 100644 --- a/docs/topics/serialization.txt +++ b/docs/topics/serialization.txt @@ -318,12 +318,12 @@ JSONL .. versionadded:: 3.2 *JSONL* stands for *JSON Lines*. With this format, objects are separated by new -lines, and each line contains a valid JSON object. JSONL serialized data look +lines, and each line contains a valid JSON object. JSONL serialized data looks like this:: - { "pk": "4b678b301dfd8a4e0dad910de3ae245b", "model": "sessions.session", "fields": { ... }} - { "pk": "88bea72c02274f3c9bf1cb2bb8cee4fc", "model": "sessions.session", "fields": { ... }} - { "pk": "9cf0e26691b64147a67e2a9f06ad7a53", "model": "sessions.session", "fields": { ... }} + {"pk": "4b678b301dfd8a4e0dad910de3ae245b", "model": "sessions.session", "fields": {...}} + {"pk": "88bea72c02274f3c9bf1cb2bb8cee4fc", "model": "sessions.session", "fields": {...}} + {"pk": "9cf0e26691b64147a67e2a9f06ad7a53", "model": "sessions.session", "fields": {...}} JSONL can be useful for populating large databases, since the data can be processed line by line, rather than being loaded into memory all at once. -- cgit v1.3