Bugs item #2958186, was opened at 2010-02-24 21:31
Message generated for change (Comment added) made by kilian3
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2958186&group_id=129076

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Sedna (current)
Status: Open
Resolution: Accepted
Priority: 3
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Ivan Shcheklein (shcheklein)
Summary: system doc $modules doesn't exist

Initial Comment:
hi there,

i'm reading the modules chapter of the prohrammers guide. it mentions a system 
document "$modules", but there is no such document in sedna 3.2. instead there 
is a collection named so. 

so long kilian


----------------------------------------------------------------------

Comment By: Kilian  (kilian3)
Date: 2010-02-25 23:58

Message:
well, in the meantime, I realized that there are documents (at least a sort
of temporary docs), which are named after the modules loaded into sedna.
they are listed within the collection of the modules in the result of the
query doc("$documents"). 
knowing that, i would now expect that
doc("$modules")
returns nearly the same as
<modules>
{
        for $m in doc("$documents")//collecti...@name='$modules']/document
        return <module>{$m/@name}</module>
}
</modules>

cheers kilian

----------------------------------------------------------------------

Comment By: Ivan Shcheklein (shcheklein)
Date: 2010-02-24 22:19

Message:
Thank you for bug report! It'll be fixed soon.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2958186&group_id=129076

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

Reply via email to