Hi Antoni,
As far as I understand you use Sedna to transform document from one representaion into another (XSLT like transformation). It's not the best task for XQuery, and unfortunately for Sedna also. It needs a lot of space to construct thousands of nodes. However, I should note that it works far from optimal in this and anyway we should work to decrease temporary memory consuming in such cases. 1. Is the 18GB temp file to be expected on such a query for such a > dataset? Maybe I should live with it and get a bigger disk. > Unfortunately, with current version of Sedna you should either rewrite your query (for example, use multiple queries one-by-one to trasform your document - temporary blocks are reused between transactions) or get a bigger disk. > 2. If I limit the temp file size with the -tmp-file-max-size option will > sedna deal with a limited temp file and bring the query to an end or > will it simply break earlier when the temp file hits the limit? > Break. We'll fix documentation to make it more clear. > Basically anything apart from 0 in the -tmp-file-max-size throws the > SE1012 error. > Ok, we'll check this. Ivan Shcheklein, Sedna Team
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
