Bugs item #1964365, was opened at 2008-05-15 10:11 Message generated for change (Comment added) made by sjoerd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1964365&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 general Group: Pathfinder CVS Head Status: Open Resolution: None Priority: 5 Private: No Submitted By: Lefteris Sidirourgos (lsidir) Assigned to: Lefteris Sidirourgos (lsidir) Summary: PF/Alg: insert..into inserts in wrong order Initial Comment: Insert .. into, inserts attributes in wrong order. Also, insert into as first/last/before/after should be tested individually in the test web with new tests for both elements and attributes. ---------------------------------------------------------------------- >Comment By: Sjoerd Mullender (sjoerd) Date: 2008-05-16 22:58 Message: Logged In: YES user_id=43607 Originator: NO The only time order matters when inserting attributes is when you're inserting the same attribute with different values multiple times into the same element. I don't know what the standard says here, but we would like the last one to stick (unless the standard prohibits this). The different order of attributes on output is purely an inconvenience. It is no shape or fashion a bug. (I would like to have an option to have the attributes produces in alphabetical order so that we can get consistent test results, but it is not a bug if the order is different. Not even if each run produces a different order.) ---------------------------------------------------------------------- Comment By: Lefteris Sidirourgos (lsidir) Date: 2008-05-16 16:32 Message: Logged In: YES user_id=1856546 Originator: YES You are right that this report is too terse to exactly know what my problem is:) but it serves more as a remainder, since I assigned this to myself. The problem is that some tests on the testweb are failing because of different attribute order than the one approved, second that the order of the insert into in the update spec is defined now (http://www.w3.org/TR/xquery-update-10/#id-upd-insert-into : The semantics of upd:insertInto are identical to the semantics of upd:insertBefore) and finally that there are not enough tests on the testweb to correctly check if insert before/as first is actually done correctly. ---------------------------------------------------------------------- Comment By: Jens Teubner (teubner) Date: 2008-05-16 16:10 Message: Logged In: YES user_id=731390 Originator: NO This report is too terse to exactly know what your problem is. But be aware that -- There is no order among attributes of the same element node. -- The order in which `insert into ...' instructions are applied to the store is undefined. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1964365&group_id=56967 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
