The problem as I see it Mecki is that we have effectively two kinds of
arrays in JSON; name/value pairs and sequential arrays. So perhaps I'm
over-complicating but it seems problematic to represent scalars, NVPs, and
sequential arrays with dynamic arrays - at least in a way that would allow
the in
DOM
kind of way.
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: 11 December 2010 23:29
To: U2 Users List
Subject: Re: [U2] Sparse array population in Pick
We also do a lot with JSON but a JSON string can go far beyond
Kevin,
I would split the data into hierarchically organized files on the U2 end
if need be.
In my experience anything past the multi-value level becomes awkward in
any Pick system if you want to use the data for reporting.
Sub values are still reasonably well handled with Basic but after that
it g
In our JSON implementation (moving information between U2 and PHP) we've
artificially limited the data coming into U2 so that it doesn't go deeper
than (effectively) multivalues. We allow the data going out of U2, however,
to be nested significantly deeper. For this product the limit isn't a
prob
To see what you can use in any particular implementation, try RAISE()
and LOWER() to see how far they go (at least those who support these
functions). I've used them before but they are indeed a pain to
manipulate. Array reference statementsdon't recognize themand
English/JQL/Retrieve/etc. don'
On 11/12/10 23:29, Kevin King wrote:
> We also do a lot with JSON but a JSON string can go far beyond attributes,
> values, and subvalues. Would be interested in Doug's take on how to extract
> something out of a JSON string without parsing it from scratch on every
> extraction, and how he would r
We also do a lot with JSON but a JSON string can go far beyond attributes,
values, and subvalues. Would be interested in Doug's take on how to extract
something out of a JSON string without parsing it from scratch on every
extraction, and how he would represent 4 or more dimensions in a MV item?
c.com
Blog: http://blog.all-spec.com
> -Original Message-
> From: Glen Batchelor [mailto:webmas...@allspec.com]
> Sent: Friday, December 10, 2010 2:38 PM
> To: 'U2 Users List'
> Subject: RE: [U2] Sparse array population in Pic
10:07 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Sparse array population in Pick
Not sure why you would lower it.
_
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more informati
that's what EV is for (unless you use another editor for data than AE) ;-)
On 10/12/2010 18:06, fft2...@aol.com wrote:
> In a message dated 12/10/2010 6:56:38 AM Pacific Standard Time,
> slestak...@gmail.com writes:
>
>
>> That is why I was thinking a real name-value store might be in order. As
In a message dated 12/10/2010 6:56:38 AM Pacific Standard Time,
slestak...@gmail.com writes:
> That is why I was thinking a real name-value store might be in order. As
> MV
> professionals, not every solution has to be a Pick solution.
>
> On Fri, Dec 10, 2010 at 4:10 AM, Symeon Breen wrote:
Yep, we do it all of time.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rob Sobers
Sent: Thursday, December 09, 2010 6:53 PM
To: U2 Users List
Subject: Re: [U2] Sparse array population in Pick
Doug,
I love JSON
rs@listserver.u2ug.org
Subject: [U2] Sparse array population in Pick
Years ago I had written a system, far predating XML, where the element-tags
were unpredictable. Essentially the user was allowed to create any tags they
wished, and any number of tags they wished, attached to another item.
Each ta
That is why I was thinking a real name-value store might be in order. As MV
professionals, not every solution has to be a Pick solution.
On Fri, Dec 10, 2010 at 4:10 AM, Symeon Breen wrote:
> Isnt this just a name value pair construct ? i do this a lot and just have
> 2 mv attributes 1 = name,
...@aol.com
Sent: 09 December 2010 22:10
To: u2-users@listserver.u2ug.org
Subject: [U2] Sparse array population in Pick
Years ago I had written a system, far predating XML, where the element-tags
were unpredictable. Essentially the user was allowed to create any tags
they wished, and any number of tags
In a message dated 12/9/2010 8:18:12 PM Pacific Standard Time,
dmc...@imb.com.au writes:
> My form is not the most efficient for random access of individual items,
> but it does give you the flexibility of being able to sort and select on
> tag/value pairs. Additional benefits are that I could a
f Dan McGrath
Sent: Friday, 10 December 2010 3:18 PM
To: U2 Users List
Subject: Re: [U2] Sparse array population in Pick
100% agree, but "this is pick" doesn't mean disregard all rules of good
DB design.
Fair enough, MVDBs are designed around not subscribing to the "1st norm
form r
users@listserver.u2ug.org
Subject: Re: [U2] Sparse array population in Pick
But Dan you're just flattening the array.
B
This is Pick!
The point of a method of populating a sparse array is to address the
efficient storage of data when your array is sparse. In your method,
you'd have t
But Dan you're just flattening the array.
B
This is Pick!
The point of a method of populating a sparse array is to address the
efficient storage of data when your array is sparse. In your method, you'd
have
to do several disk reads in order to collect all the tags for one item in one
spo
previous file.
Regards,
Dan
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
fft2...@aol.com
Sent: Friday, 10 December 2010 1:28 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Sparse array population in Pick
In a mes
In a message dated 12/9/2010 6:18:24 PM Pacific Standard Time,
dmc...@imb.com.au writes:
> You could quite easily come up with an escaping scheme to convert any
> tag name into a valid escaped dictionary name.
>
Could you explain this more clearly?
I don't understand what you mean.
___
:08 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Sparse array population in Pick
No David you cannot restrict the tag names to valid Dict names, they can
be anything the user could possibly think up. And the user's can think
up a lot of things!
Think of the tags that you can app
Wouldn't be difficult to make a json encoder/decoder in Unibasic.
Something I have been toying with is using Redis with Unidata. I
wrapped Set and Get in pcperform statements. Works quite well.
I do not propose this for permanent storage, but could have some use in
report generation and cac
No David you cannot restrict the tag names to valid Dict names, they can be
anything the user could possibly think up. And the user's can think up a
lot of things!
Think of the tags that you can apply on Amazon to products. You are not
forced to pick your tags from a list, you can type in any
the tag names to valid dictionary names you could
> > do something like:
> >
> > TAGS DICT:
> > 1052_MAKE
> > 1052_MODEL
> > 1052_AGE
> >
> > TAGS DATA:
> > 001 Chrysler
> > 002 LeBaron
> > 003 7 years and 3 days
> >
>
on. In JavaScript it takes around 7 to 10 milliseconds to parse a
pretty big JSON string into a JSON array.
Regards,
Doug
www.u2logic.com/tools.html
-Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rob Sobers
Sent: Thursday, December 09
2-users-boun...@listserver.u2ug.org] On Behalf Of fft2...@aol.com
> Sent: Thursday, December 09, 2010 3:10 PM
> To: u2-users@listserver.u2ug.org
> Subject: [U2] Sparse array population in Pick
>
> Years ago I had written a system, far predating XML, where the element-tags
> wer
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of fft2...@aol.com
Sent: Thursday, December 09, 2010 3:10 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Sparse array population in Pick
Years ago I had written a system, far predating XML, where the element-tags
were
Will,
I used the second model (originally about 20 years ago) with the initial
empty value. Neither model is really very simple, but with the second model
we created one or two I-descriptor subroutines that can allow dictionaries
to be tailored to any tag you want to look for and select for all v
Years ago I had written a system, far predating XML, where the element-tags
were unpredictable. Essentially the user was allowed to create any tags
they wished, and any number of tags they wished, attached to another item.
Each tag had an associated value. So far example
Zip Code = 9506
30 matches
Mail list logo
