in reply to More XML-Twig

It is hard to tell what's going on without looking at the XML. Is ACCOUNT within MEMBER, or vice-versa? twig_roots would not like that.

BTW, Do you really need to use twig_roots? It seems that generally, users tend to use it in cases where it is not needed. In your case, you should probably only use it if ACCOUNT and MEMBER make up just a small part of the entire XML flow, and you don't want to load the rest of the document. If your XML is mostly a list of ACCOUNT and MEMBER, then there is no need to use twig_roots. Even if it is appropriate in your case, I hope that others will read this warning and think twice before using twig_roots ;--)

Replies are listed 'Best First'.
Re^2: More XML-Twig
by zacc (Novice) on Jan 08, 2008 at 15:50 UTC
    Sorry, should have been clearer, the XML is in the form...
    <ROOT> <MEMBER>....</MEMBER> <MEMBER>....</MEMBER> <ACCOUNT>...</ACCOUNT> <ACCOUNT>...</ACCOUNT> <ACCOUNT>...</ACCOUNT> </ROOT>
    ie the whole file is (at this time) simply made up of MEMBER and ACCOUNT elements. MEMBER records are processed by one routine, ACCOUNT records are processed by a separate routine.
    (I probably don't need twig_roots at this stage, but I've set it up for future use when the file will contain loads of other elements and then I can use it to reduce the overall load on the system)
    Thanks