Bugs item #1981762, was opened at 2008-06-02 09:10 Message generated for change (Comment added) made by lsidir You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1981762&group_id=56967
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: PF/tests Group: Pathfinder CVS Head Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Manegold (stmane) Assigned to: Jan Rittinger (tsheyar) Summary: PF/alg: "Mapping unique name to an original name failed." Initial Comment: With the Algebra back-end, several tests fail with ERROR = !fatal error: Mapping unique name to an original name failed. (unique =..., free=(NULL)) E.g., http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_R/Q05o.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQUF_AddressBook/Q1x.err.00.html ---------------------------------------------------------------------- >Comment By: Lefteris Sidirourgos (lsidir) Date: 2008-08-14 11:05 Message: Logged In: YES user_id=1856546 Originator: NO Another affect of this bug is described in bug report: [ 1983333 ] PF/alg: tests/W3C_use_cases/XQUF/AddressBook/check_doc fails <https://sourceforge.net/tracker/index.php?func=detail&aid=1983333&group_id=56967&atid=482468> In reality, test tests/W3C_use_cases/XQUF/AddressBook/Q1x is failing in the stable version only for 32 bit machines since the workaround works for 64-bit machines, while in the current version fails with the same message as this bug report: !fatal error: Mapping unique name to an original name failed. (unique =item3396, free=(NULL)) ---------------------------------------------------------------------- Comment By: Jan Rittinger (tsheyar) Date: 2008-06-02 13:58 Message: Logged In: YES user_id=993208 Originator: NO This bug report probably describes the problem best. For some queries the rewrites are so good that we run out of bit-encoded column names. A complete overhaul of the optimization and property inference phases is needed here. For the release I checked in a fallback solution that at least avoids errors. For the head the resolution is pending. This bug report supersedes http://sourceforge.net/tracker/index.php?func=detail&aid=1981491&group_id=56967&atid=482468 http://sourceforge.net/tracker/index.php?func=detail&aid=1908822&group_id=56967&atid=482468 ---------------------------------------------------------------------- Comment By: Jan Rittinger (tsheyar) Date: 2008-06-02 13:00 Message: Logged In: YES user_id=993208 Originator: NO This bug report probably describes the problem best. For some queries the rewrites are so good that we run out of bit-encoded column names. A complete overhaul of the optimization and property inference phases is needed here. For the release I checked in a fallback solution that at least avoids errors. For the head the resolution is pending. This bug report supersedes http://sourceforge.net/tracker/index.php?func=detail&aid=1981491&group_id=56967&atid=482468 http://sourceforge.net/tracker/index.php?func=detail&aid=1908822&group_id=56967&atid=482468 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1981762&group_id=56967 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
