Re: results of SPLIT when keys not unique

2017-11-03 Thread Jim Lambert via use-livecode
> Monte wrote: > > Perhaps something like: > > split by and [{replacing | > splitting | ignoring} duplicates] Yes. +1 Jim Lambert ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and

RE: results of SPLIT when keys not unique

2017-11-02 Thread Ralph DiMola via use-livecode
] Sent: Thursday, November 02, 2017 6:49 PM To: rdim...@evergreeninfo.net Cc: How to use LiveCode Subject: Re: results of SPLIT when keys not unique On Thu, Nov 2, 2017 at 3:45 PM, Ralph DiMola <rdim...@evergreeninfo.net> wrote: > Whoops, not tested and I saw an error. > > Select myt

Re: results of SPLIT when keys not unique

2017-11-02 Thread Dr. Hawkins via use-livecode
On Thu, Nov 2, 2017 at 3:45 PM, Ralph DiMola wrote: > Whoops, not tested and I saw an error. > > Select mytable.animalname,mytable.animalnumber from (select distinct > mytable.animalname from mytable as mytable2) left join mytable on > mytable.animalname =

Re: results of SPLIT when keys not unique

2017-11-02 Thread Bob Sneidar via use-livecode
The last one of course. Bob S > On Nov 2, 2017, at 15:39 , Monte Goulding via use-livecode > wrote: > > A quick test and it looks like split will clobber any new elements with the > same key as those previously parsed. The docs state that only one element >

Re: results of SPLIT when keys not unique

2017-11-02 Thread Dr. Hawkins via use-livecode
On Thu, Nov 2, 2017 at 3:39 PM, Monte Goulding via use-livecode wrote: > It would probably be nice to have some explicit syntax to govern this > behavior so that you could explicitly declare > you want clobbering behavior or first come best dressed. explicit is

Re: results of SPLIT when keys not unique

2017-11-02 Thread Dr. Hawkins via use-livecode
On Thu, Nov 2, 2017 at 3:45 PM, Ralph DiMola wrote: > Whoops, not tested and I saw an error. > > Select mytable.animalname,mytable.animalnumber from (select distinct > mytable.animalname from mytable as mytable2) left join mytable on > mytable.animalname =

Re: results of SPLIT when keys not unique

2017-11-02 Thread Monte Goulding via use-livecode
> On 3 Nov 2017, at 9:39 am, Monte Goulding wrote: > > It would probably be nice to have some explicit syntax to govern this > behavior so that you could explicitly declare you want clobbering behavior or > first come best dressed. Oh… one might also feasibly want output

RE: results of SPLIT when keys not unique

2017-11-02 Thread Ralph DiMola via use-livecode
Whoops, not tested and I saw an error. Select mytable.animalname,mytable.animalnumber from (select distinct mytable.animalname from mytable as mytable2) left join mytable on mytable.animalname = mytable2animalname Ralph DiMola IT Director Evergreen Information Services

RE: results of SPLIT when keys not unique

2017-11-02 Thread Ralph DiMola via use-livecode
Would something like this work? Select mytable.animalname,mytable.animalnumber from (select distinct mytable.animal from mytable as mytable2) left join mytable on mytable.animalname = mytable2animalname Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net

Re: results of SPLIT when keys not unique

2017-11-02 Thread Monte Goulding via use-livecode
A quick test and it looks like split will clobber any new elements with the same key as those previously parsed. The docs state that only one element will be created but are unclear about which element value will be retained. It would probably be nice to have some explicit syntax to govern this