Chip, This might be useful: https://developer.ibm.com/answers/questions/421044/how-to-write-regular-expression-for-nested-json-ev/
The sentiment in the last post, "...I don't know of a good way. Here is a bad way that might be enough" is echoed in a lot of the responses to similar questions I saw on StackOverflow. It's probably an OK way to simply verify the property is there. On Tue, Oct 22, 2019 at 8:42 AM Chip Scheide via 4D_Tech < [email protected]> wrote: > I am just getting started playing/using objects. > > I wrote some routines to determine if a particular property/value > exists either in an object, or in an object which is part of an object > array. > > Given: > - the object is complex, i.e. has 1 or more sub-objects included and/or > an object array included > - the only interest is does the property/value pair exist (true/false) > > It occurred to me last night, that this processes maybe significantly > faster, and less complicated, by simply converting the complex object > to text (JSON Stringify) and then use POSITION to locate the > property/value pair. > > Has anyone looked at this? is using JSON faster? slower? no difference? > or 'it depends'? > other comments? > > Thanks > Chip > We have done so much, with so little, for so long; > We are now qualified to anything with nothing <sigh> > - unknown > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- Kirk Brooks San Francisco, CA ======================= What can be said, can be said clearly, and what you can’t say, you should shut up about *Wittgenstein and the Computer * ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
