Hi Ivan, Sorry for delay in replying on this issue. You and the Sedna Team have been so efficient in rectifying bugs over the last week that I've been finding it difficult to keep abreast of my retesting schedule :-)
Anyway, with some effort I've managed to strip down the offending modules to the absolute minimum needed to manifest the problem. It certainly seems to be a bug rather than incorrect XQuery code and so I've have lodged a formal ticket for it together with XQuery code and (Linux) shell script to reproduce. Best regards, Justin Johansson Ivan Shcheklein wrote: > Hi Justin, > > Could you send us these modules to try to reproduce the issue? > > Ivan Shcheklein, > Sedna Team > > On Sat, Aug 15, 2009 at 3:24 AM, Justin Johansson <[email protected] > <mailto:[email protected]>> wrote: > > Hello Sedna Team, > > Having just added a 5th XQuery Library Module (and consequently a 5th > unique module namespace) to my Sedna XQuery application, the executor > now raises ERROR SE5100 - Error in Scheme part - parameter limit > exceeded when attempting to run a query which imports this new module. > ... > ------------------------------------------------------------------------------ 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
