I'm in V16 and have a good use for an object field. Specifically, for
storing objects ;-) I haven't yet done any research on 4D's object fields
regarding performance or storage space, and I hoping that someone has given
me a head start.
For background, the objects I'm storing are non-relational ex
The question posed to me when I asked was: "Why do you want a 32bit server?
64bit is far superior"
There's not many, but there's a few 32bit servers out there...
😉
Randy Engle
XC2 Software LLC – XC2LIVE!
-Original Message-
From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On B
> On Jul 9, 2017, at 6:00 AM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Any idea about storage requirements for objects? They're shown as JSON but
> are presumably stored in a more efficient binary format of some kind that
> takes less space.
The last time I examined the resu
Okay, I've got a crude finding on one of my questions.
I had been storing an array of objects as text in a text field. Following
Cannon's suggestion on a nearby thread, I wrapped the array in an object
and stored that instead. Much messing around with 'corrupt' data files
later (see below), I was
I don't think there is any difference between what you call text and binary,
what you report sounds more like the difference between UTF-16 and UTF-8.
technically, the 2:1 ratio you describe is variable,
but I understand for all practical purposes in ASCII,
you could say that it is pretty much a c
> I don't think there is any difference between what you call text and
binary,
> what you report sounds more like the difference between UTF-16 and UTF-8.
That would make sense of the numbers. And the slight varience from a
perfect 1:2 ratio may come from the wrapper element stored in the object
v
As a point of interest, that 12.35 GB export? Using 7Zip, the compressed
size is 6.6 MB. Yes, a fraction of 1% of the original size. And that's not
using the most aggressive compression mode.
**
4D Internet Users Group (4D iNUG)
F
> 2017/07/09 20:00、David Adams via 4D_Tech <4d_tech@lists.4d.com> のメール:
>
> {
> "date":"2017-01-01",
> "items_total": 37,
> "request_max": 12,
> "request_min: 0
> }
an object is not just an opaque container of JSON string.
a date value is converted to ISO string (so it is larger, if you focus
but I think the term "hash table" has only been mentioned in describing how the
keys are indexed stored, not the values.
> 2017/07/10 13:48、David Adams via 4D_Tech <4d_tech@lists.4d.com> のメール:
> So, do you know anything about the indexing scheme? Or anything about the
> hash table?
*
On Mon, Jul 10, 2017 at 3:40 PM, Keisuke Miyako via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> but I think the term "hash table" has only been mentioned in describing
> how the keys are indexed stored, not the values.
>
Okay. But has 4D said or documented *anything* of practical use or general
inte
10 matches
Mail list logo