| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: PIZZA time again :-)
"mAsterdam" <mAsterdam_at_vrijdag.org> wrote in message news:4318b45c$0$11069$e4fe514c_at_news.xs4all.nl...
> vc wrote: >> mAsterdam wrote:
>> >> Since 'merge' is commonly defined for lists with the same ordering, the >> function cannot be applied to lists with different orderings, e.g [a, >> b] and [b,a,c] (ordering is defined by an element position in the list) >> clearly cannot be merged. > > That is the merge as used in some sorting algorithms, not a merge > in it's own right. But if you feel more comfortable calling the discussed > merge mymerge, truemerge, falsemerge or > order_preserving_merge - ok.
That is the merge function as used in functional languages like ML, Haskell or Lisp (not pure functional). My response relied on the common usage in those languages.
Now, what is "a merge in its own right" ? Unless one defines 'merge_in_its_own_right', one cannot answer the question what 'merge_in_its_own_right' should do with lists where ordering is defined by an element position. Received on Fri Sep 02 2005 - 16:05:02 CDT
![]() |
![]() |