Re: Scope of entity selection

2018-10-18 Thread Peter Bozek via 4D_Tech
On Thu, Oct 18, 2018 at 2:30 PM Christian Sakowski < christian.sakow...@heubach-media.de> wrote: > > > I did not find a way how to do a shared collection from selection, > > You don’t need this. Just pass the object into the process. The object will be copied. > If you have performance problems,

Re: Scope of entity selection

2018-10-18 Thread Chip Scheide via 4D_Tech
Christian, I *think* that the intent was to pass an ordered collection from process to process. i.e. - process 1 order the data in whatever manner is desired. - pass the collection from process 1 to process 2 - process 2 receive the ordered collection and do stuff with it, in the order in which

Re: Scope of entity selection

2018-10-18 Thread Christian Sakowski via 4D_Tech
> I did not find a way how to do a shared collection from selection, You don’t need this. Just pass the object into the process. The object will be copied. If you have performance problems, please let me know your benchmarks. > creates unordered selection, so order is lost.

Re: Scope of entity selection

2018-10-18 Thread Peter Bozek via 4D_Tech
On Sat, Oct 13, 2018 at 10:29 PM Christian Sakowski via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > > like: > $object.myIDs:=$entitySelection.toCollection("ID“).extract(„ID“) > new process(…;$object) > > and in the new process just create the new entity selection: > > ds.Table.query(„ID IN

Re: Scope of entity selection

2018-10-13 Thread Kirk Brooks via 4D_Tech
Peter, Collections are ordered. So just sort the entity selection first. On Sat, Oct 13, 2018 at 2:40 PM Peter Bozek via 4D_Tech < 4d_tech@lists.4d.com> wrote: > On Sat, Oct 13, 2018 at 10:29 PM Christian Sakowski via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > >

Re: Scope of entity selection

2018-10-13 Thread Peter Bozek via 4D_Tech
On Sat, Oct 13, 2018 at 10:29 PM Christian Sakowski via 4D_Tech < 4d_tech@lists.4d.com> wrote: > $object.myIDs:=$entitySelection.toCollection("ID“).extract(„ID“) > new process(…;$object) > > and in the new process just create the new entity selection: > > ds.Table.query(„ID IN :1“;$object.myIDs)

Re: Scope of entity selection

2018-10-13 Thread Christian Sakowski via 4D_Tech
> If not, you could try LONGINT ARRY FROM SELECTION and pack the array into > shared object. Bad idea. First, you should avoid strongly shared objects in this case. Second, LONGINT ARRY FROM SELECTION has nothing to do with ORDA. Third: entities are process depended, because they may use

Re: Scope of entity selection

2018-10-13 Thread Alan Chan via 4D_Tech
Hi Peter, I haven't touched v17 yet. There might be easier way. If not, you could try LONGINT ARRY FROM SELECTION and pack the array into shared object. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >This may be related to other thread - Defining and documenting objects - as >it

Scope of entity selection

2018-10-13 Thread Peter Bozek via 4D_Tech
This may be related to other thread - Defining and documenting objects - as it is related to scope of new objects: I am playing a bit with 4D v17, and, if I understand it correctly, I can pass around shared objects and shared collection between processes (and workers, but I am not that far yet.)