Hi France,
With the new trigger mechanism, your trigger will launch your "add-id" function whenever a document is changed in the database. However, there will never be loops, because a trigger function will never trigger any other functions.
Hope this helps, Christian
A writer modifies an .xml file and saves the changes. An event that can be caught by an xquery function is triggered. My xquery function adds an @id to all elements that don't have one and saves the document again. There is a way to differenciate users 'replace' from query 'replace' so that if an event is triggered again here, we will not loop indefinitely.
I know you are working on triggers, but I'm not sure it applies to this use case. Can this currently be done?
Thanks!
-- France Baril Architecte documentaire / Documentation architect france.baril@architextus.com