I agree. I had just read this article the other day, however, and was hoping (expecting) that 4D would provide something similar to Postgres JSONB and GIN indexes:
https://compose.com/articles/is-postgresql-your-next-json-database/ -- Jeffrey Kain [email protected] > On Sep 12, 2017, at 5:39 PM, David Adams via 4D_Tech <[email protected]> > wrote: > > Seriously people, 4D's hostility to the relational model has been around > since longer than I have, and it makes no sense. The beauty of normalized > data is that you can easily answer *unanticipated questions.* Also, you can > store your information in a way that's easy to keep in order. The problem > with subtables wasn't just the implementation of the idea, it was the idea > itself. Object fields for relational data? Much the same. ********************************************************************** 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:[email protected] **********************************************************************
