Simply put, preemptive triggers are not for client/server operations even all the codes are preemptive-compliant.
- data entry UI and do entry data - click a button call a method that contains SAVE RECORD that invoke trigger in server and all codes in this method itself and codes in trigger are all preemptive-compliant - In this case, trigger won't be preemptive because the method above was called from UI. Am I correct? TIA Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >I agree it would be nice to eventually have preemptive mode on the client >side, but I also think the subject needs to be discussed in context. > >Preemptive mode makes it possible to run multiple processes independent of >each other concurrently, so the primary benefactor should be the server. > >After all, preemptive processes can't have a UI, neither can it sync with >other processes (without using semaphores etc.), so in many ways its like a >stored procedure (and not a method with the “execute on server” property.) > >2018/07/12 13:36、Alan Chan via 4D_Tech ><4d_tech@lists.4d.com<mailto:4d_tech@lists.4d.com>>のメール: >Of course, SAVE RECORD, DELETE RECORD is needed to invoke trigger. However, >the method that call SAVE RECORD would be executed in 4D Remote and 4D Remote >isn't supported. A dead lock? > > > >********************************************************************** >4D Internet Users Group (4D iNUG) >FAQ: http://lists.4d.com/faqnug.html >Archive: http://lists.4d.com/archives.html >Options: https://lists.4d.com/mailman/options/4d_tech >Unsub: mailto:4d_tech-unsubscr...@lists.4d.com >********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
