Why that ? Because for the moment, I don't need any information about "items", but I want to collect this information and store it in my QVD, so that I will be able to parse it later if needed.
Have in mind that the node I want to store as it is is more complicated as in this example. It could contain other nodes which could contain other nodes... which would give me many tables linked each one to others, when I just need a way to store the information for later use.
The easy way out is to simply store the item table to a qvd and drop it. When you need the data you can simply load the data from the qvd. It will be linked automatically using the Key_student_C932B46F5721DF6Dfield.
Thx, I agree, in my example, this could be the easiest way.
In my real case, it would not be one extra table to store as QVD, but many more, because of the structure of my xml node (tables in tables...), and as many QVD files to maintain on every update made by my collector...