Bill,
Given that we now have a viable option for storing date/time values in a
single field (eg: string(date;ISO date;time)) why not just modify your
structure, create a new field and write both values to it. Even if you
decide to retain the discrete date & time fields this is not much overhead
On Thu, Mar 8, 2018, at 11:17 AM, Keisuke Miyako via 4D_Tech wrote:
> OB Copy with pointers is effectively the "record to object" feature.
Ahh - that's useful. Now if only 4D supported pointers to methods. :)
Here's the specific issue: I have a record (many, actually heh) that has this
sort of
it's not often the case that you'd need all the fields represented in the
object.
on top of that, sometimes the structure defined field names or even their order
of appearance may not be ideal.
OB Copy with pointers is effectively the "record to object" feature.
> On Mar 8, 2018, at 15:41, Bill Hutten via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
>> On Thu, Mar 8, 2018, at 10:31 AM, Christian Sakowski via 4D_Tech wrote:
>>
>> have you looked at "Selection to JSON" and "JSON TO SELECTION"? But it
>> will not cover all field types.
>
> Yeah - I'm
On Thu, Mar 8, 2018, at 10:31 AM, Christian Sakowski via 4D_Tech wrote:
> have you looked at "Selection to JSON" and "JSON TO SELECTION"? But it
> will not cover all field types.
Yeah - I'm currently doing: "Selection to JSON" and then "JSON PARSE ARRAY" but
that's kindadumb. Also there's
:27 schrieb Bill Hutten via 4D_Tech <4d_tech@lists.4d.com>:
>
> I admit I've not been keeping 100% up to date with the many language changes
> in 4D v16 - so before I go write a bunch of test code (or worse, read the
> documentation) - do current versions of 4D have commands
I admit I've not been keeping 100% up to date with the many language changes in
4D v16 - so before I go write a bunch of test code (or worse, read the
documentation) - do current versions of 4D have commands to convert from a
record to an object, or selection to object array, and ideally vice
7 matches
Mail list logo
