This may have been a Beta issue. This was a script that I created in the 3.2 Beta release. Initially the same results were appearing in the official 3.2 public release from last week. However, after a shutdown and a refresh of my workspace, the nested loop seems to be working as expected in current the 3.2 release. I'll let you know if I see anything unexpected again with the nested loops.
Thanks, Catrina On Nov 6, 2:23 pm, Scott Henninger <[email protected]> wrote: > Catrina; Yes, an IterateOverSelect can have another IterateOverSelect > in the body. Without further information, I'd suggest taking a close > look at variable bindings to see if there is some confusion there (?) > > -- Scott > > On Nov 6, 11:09 am, Catrina <[email protected]> > wrote: > > > > > I’m encountering some unexpected behavior with a nested loop using > > Iterate Over Select modules. I’m currently working with TBC 3.2.0. > > > When the inner loop goes on to the next iteration, it appears that > > processing moves to the outer loop. Usually (such as in Java and > > other programming languages) processing for each iteration within the > > nested loop continues in the inner loop. > > > I have something like the following in my script: > > IterateOverSelect_1 --> logging module --> IterateOverSelect_2 --> > > logging 2 module > > > Are nested loops allowed in SPARQLMotion scripts? > > > Thanks, > > Catrina- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
