#community-help

Storing JSON Objects: Stringify Vs Break Up

TLDR Ricardo inquired regarding the best method to store a JSON object. Kishore Nallan suggested stringifying and storing if no search on the object is required.

31mo

Join the chat

May 08, 2021 (31 months ago)

Photo of md5-a2785b9d22ba23f3627d4bd877e95e7c

Ricardo

03:04 PM

if i need to store something that is a json object. what's the best approach stringify it and store it as one piece. or break it up into multiple fields (int32 and string)? I will always be returning it all together.

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

04:04 PM

If you are not planning to search on the JSON object you can just stringify and store it.

04:04

Kishore Nallan

04:04 PM

And just ensure that the field is not part of the schema and it won't be indexed.

Ricardo

05:27 PM

awesome, thanks again Kishore Nallan

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Optimizing JSON Data Import and Search with PHP Library

Arumugam experienced slow search results and data import time with json and PHP library. Kishore Nallan advised trying import and provided guidance on integrating the function into a PHP application. The issue was resolved as the search results are now displayed faster.

22mo

Fixing "bad json" error in Typesense 0.24

Adam experiences "bad json" error when creating collections in Typesense 0.24. Jason identifies a typo in the docs causing the error and helps troubleshoot additional errors.

7mo

Discussing Document Indexing Speeds and Typesense Features

Thomas asks about the speed of indexing and associated factors. The conversation reveals that larger batch sizes and NVMe disk usage can improve speed, but the index size is limited by RAM. Jason shares plans on supporting nested fields, and they explore a solution for products in multiple categories and catalogs.

20mo