In my mind a variable is the same thing as a key value pair. The variable name
is the key and the data the variable contains is the value. I name all
variables with a user readable name so what is the difference between a
variable named vFirstName that contains “John” and oObj.firstname that
Hi Bob,
i will tell a little story that aligns perfectly with what you told:
I have a huge database system for managing car spare parts.
each part can be of a specific type, thus having specific descriptive criteria
each part can be linked to any number of vehicles, sometimes with a specific
Along the lines of, "what is an appropriate use of an object field", I've
been considering this:
We are a manufacturing company with lots of tools and lots of products.
Each tool has various attributes, but each tool type has a different set
of characteristics.
Silly example that I hope
Since the feature of object fields is very near the concept of NoSQL databases
like MongoDB and so on (at least it is partly stolen from their) ...
I think the following article by Sarah Mei summarizes the discussion in the
this thread in a way:
On Tue, Sep 12, 2017 at 11:07 PM, Jeffrey Kain via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Yeah, so many caveats to object fields. Bite the bullet, use a related
> table...
>
>
Well, I wrote that i am playing with it, Testing how it can be used, what
commands are available and where are
> Here´s my real-world use:
> I wrote an iPhone app that collects data (scans barcodes).
> That data is in JSON format and transferred via HTTP to a 4D Server.
> The server stores that data in an object field (which is never queried. It
> just holds the collected data).
That's a great example of
David Adams:
> I've been asking about real-world use of object fields for quite some time
Here´s my real-world use:
I wrote an iPhone app that collects data (scans barcodes).
That data is in JSON format and transferred via HTTP to a 4D Server.
The server stores that data in an object field
> On Sep 12, 2017, at 5:48 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Exciting stuff. I've read a ton about it and done some tests. Rob's plugin
> doesn't have an explicit command for transferring object fields, but you
> can stringify them and send them as text.
Most
On Wed, Sep 13, 2017 at 9:25 AM, Tim Nevels via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> On Sep 12, 2017, at 5:49 PM, Jeffrey Kain wrote:
>
> > Yeah, so many caveats to object fields. Bite the bullet, use a related
> table...
>
> Remember 4D’s implementation strategy for new features:
>
> - You
On Sep 12, 2017, at 5:49 PM, Jeffrey Kain wrote:
> Yeah, so many caveats to object fields. Bite the bullet, use a related
> table...
Remember 4D’s implementation strategy for new features:
- You get a little bit at a time.
- The feature set is not complete.
- The public (i.e. 4D developers)
That's a good article, if you want more - ping me. And that's exactly the
idea I was referring to when I said I'd be willing to learn some new
operators if it bought me a lot. And, since I tend to write like I know
what I'm talking about no matter if I do or don't ;-) At the least, John
DeSoi and
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
jeffrey.k...@gmail.com
> On Sep 12, 2017, at
Jeff,
Well, thanks for trying to be the cranky old man instead of me. But just
won't do. Now I have to rant.
My skepticism regarding using object fields for the purposes should be
pretty obvious to anyone that's paid attention.
Regarding the Summit demo...I watched the video and thought that it
Yeah, so many caveats to object fields. Bite the bullet, use a related table...
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Sep 12, 2017, at 5:03 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
>> I am playing with idea to use object for values that are used only for
>> display /
On Wed, Sep 13, 2017 at 3:22 AM, Peter Bozek via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> On Tue, Sep 12, 2017 at 7:10 PM, Herr Alexander Heintz via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
>
>
> I am playing with idea to use object for values that are used only for
> display / searching. I
On Tue, Sep 12, 2017 at 7:10 PM, Herr Alexander Heintz via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> Absolutely.
> I exclusively use object fields for additional data and storage of
> connected information to a specific data row, such as record and field
> history, specific item settings etc.
>
Absolutely.
I exclusively use object fields for additional data and storage of connected
information to a specific data row, such as record and field history, specific
item settings etc.
All of these will NOT be queried on.
There are cases where I use object fields for variable data structures,
So disappointing.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Sep 12, 2017, at 12:14 PM, Herr Alexander Heintz via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Having worked with 4D since ages long forgotten, I would have to feel very
> lucky and outright daring to even assume such a thing
Am 12.09.2017 um 17:22 schrieb Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>:
>
> Trying to figure out why our experience with QUERY BY ATTRIBUTE is so
> different than the demos at the last 4D Summit.
>
> We're running 4D Server 16.2 64-bit on Windows. The Invoices table has about
> 9
That was my first thought too, but I can change the query string to "Ralph" and
it still does a sequential scan of the table, returning no rows.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Sep 12, 2017, at 11:26 AM, Spencer Hinsdale via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> isn't there
2, 2017 5:23 PM
> To: 4d_tech@lists.4d.com
> Cc: Jeffrey Kain <jeffrey.k...@gmail.com>
> Subject: QUERY BY ATTRIBUTE is slow af
>
> Trying to figure out why our experience with QUERY BY ATTRIBUTE is so
> different than
> the demos at the last 4D Summit.
>
> We're runnin
isn't there some trick to use a character code instead of at?
and does the "beginning and end" pref possibly apply?
> On Sep 12, 2017, at 8:22 AM, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> Trying to figure out why our experience with QUERY BY ATTRIBUTE is so
> different
Trying to figure out why our experience with QUERY BY ATTRIBUTE is so different
than the demos at the last 4D Summit.
We're running 4D Server 16.2 64-bit on Windows. The Invoices table has about 9
million rows, and we added an index to the Extra field in this table which is
an object field.
23 matches
Mail list logo
