Bugs item #2836184, was opened at 2009-08-12 16:09 Message generated for change (Settings changed) made by allexk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2836184&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: Query Execution Group: Sedna (development) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Justin Johansson (justinjohansson) Assigned to: Alexander Kalinin (allexk) Summary: Query incorrectly raises ERROR XQST0073 relating to imports Initial Comment: Sedna Version 3.2.43 Scenario: Two modules from the same namespace mutually import each other. When a query is run which imports from said namespace, Sedna erroneously raises ERROR XQST0073. Reproduce with: LOAD OR REPLACE MODULE "a.xqlib" LOAD OR REPLACE MODULE "b.xqlib" where a.xqlib contains: xquery version "1.0"; module namespace my = "http://foobar.com/";; import module "http://foobar.com/";; declare function my:a() { () }; and b.xqlib contains: xquery version "1.0"; module namespace my = "http://foobar.com/";; import module "http://foobar.com/";; declare function my:b() { () }; Then in command client: Welcome to term, the SEDNA Interactive Terminal. Type \? for help. q.com> import module "http://foobar.com/";; > > ()& SEDNA Message: ERROR XQST0073 It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace. Details: Cycle in module import: http://foobar.com/, http://foobar.com/ Note that the namespace-uri's reported in the alleged cycle are exactly the same. According to the XQuery spec, this error should only be raised if the mutually importing modules do not share a common namespace (as the error message correctly explains). Cheers Justin Johansson ---------------------------------------------------------------------- >Comment By: Alexander Kalinin (allexk) Date: 2009-08-22 12:54 Message: Fixed in the new development build. ---------------------------------------------------------------------- Comment By: Ivan Shcheklein (shcheklein) Date: 2009-08-15 14:25 Message: Justin, thank you for bug report! This is a know problem in semantic analyzer. We are working on a new SA at present which is written completely in C/C++. This bug will be fixed also. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=2836184&group_id=129076 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
