On Tue, Apr 22, 2008 at 12:10:05PM +0200, ewilde wrote:

hi,

first: about that bug, i'll defiantly file it.

second:

when i migrated this table from mssql to monetdb5 I intentionally inserted it in that order (recid,ft,val). i used COPY INTO while supplying a file that i prepared in advanced with such a sorting.

when i first decided to test monetdb5 i did it because i understood it should perform better than row-oriented DBMSs (like mssql), especially in CRM-like applications. so... i now understand that monetsdb5 is actually being expected to perform BAD in that specific situation i described before (in my previous message).

from my experience in building CRM applications, that kind of "left join" according to unique number (recid) is very common in CRM applications. am i missing something here??

If your data is sorted, MonetDB should just work fine here. So on which version of MonetDB did you test this? Is it possible I could repeat your experiment somehow? Niels

Thanks again,

ewilde.

------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao... _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

-- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl