If storage space is a primary constraint and object indexing is not needed, you can use a blob to store as UTF-8 text.
VARIABLE TO BLOB with object uses UTF-8 text (tested 15.4, not 16). In your example where you basically wanted to store an object array directly, you could stringify the array then text to blob field with UTF-8. John DeSoi, Ph.D. > On Jul 13, 2017, at 11:21 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > * The previous point is _only_ a concern to people (like me) that are > trying to store and process a lot of data. Also (in my case), I'm storing > fully prepared JSON for export to/interaction with other systems. So, using > tables as a JSON repository, not because there is any reason to search the > JSON. The JSON is an output product. In such a case, it makes sense to push > the data out to something where you can use a smaller character set > (Latin1, UTF8), if you can get away with it. If you're storing Chinese > surnames, you need UTF16 (I think), if you're storing numbers, you may only > need Latin1. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
