On Tue, Jul 11, 2017 at 3:10 AM, David Adams via 4D_Tech < 4d_tech@lists.4d.com> wrote:
> * Use a header object that describes the 'columns' and then use compact > JSON arrays for the data. Rob Laveaux reminded me about this option some > months back and it's a really decent compromise. > That seems like a good option - it's the same, mostly, as a TSV/CSV. But it seems like JSON isn't appropriate for your storage needs (compactness trumps all), irrespective of how 4D stores it internally. ********************************************************************** 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 **********************************************************************
