I have been reading about MonetDB for a few days now, and have played
around with it some and it seems to solve some of the ultra complex
queries that I'd like to do in a time that is amazing. Congrats! One
thing, though, that confuses me is some scaling issues.
The data set that I'm looking at is potentially in the billions of
traditional rows, with about 50 columns, so from my understanding
that'd be 50 different BATs each with a billion or more items. My
concern is that OIDs seem to be restricted to 2^32-1, although from
looking at virtual OIDs, it's unclear whether in my situation that
would be useful?
Any thoughts on stuffing that much data into the system, especially
how it might impact dealing with VM issues? I'm more than happy to
say "this is the wrong approach" or system for this problem, as this
is obviously a non-normal case.
Chris
--
| Christopher Petrilli
| petrilli(a)gmail.com
Hi,
I've compiled MonetDB and the SQL front-end on my PowerMac 2x2 G5.
I've used fink to install the libraries needed. I would like to perform
the query test that are available from http://benchw.sourceforge.net .
How can I use the acsii_io module to bulk load the data files from the
benchw project?
Thanks in advance.
Regards,
Juan José.
(I am not the one with the problem here, but reporting on behalf to
stick to the protocol. Please ignore your user agent's default reply to
address and send replies to the list, not to me.)
The following build error appears for a user that compiles on a Mac:
gcc -g -O2 -std=c99 -Wall -W -Werror-implicit-function-declaration
-Werror -Wno-format -Wno-unused-function -Wno-unused-label
-Wno-uninitialized -D_REENTRANT -o .libs/MapiClient MapiClient.o
ReadlineTools.o -L/sw/lib ./.libs/libMapi.dylib
/Users/rvjansen/Desktop/MonetDB/src/common/.libs/libstream.dylib
-lreadline ../../../common/.libs/libmutils.dylib
../../../common/.libs/libstream.dylib
/Users/rvjansen/Desktop/MonetDB/src/common/.libs/libmutils.dylib -lz
/sw/lib/libiconv.dylib
ld: Undefined symbols:
_BZ2_bzclose
_BZ2_bzflush
_BZ2_bzopen
_BZ2_bzread
_BZ2_bzwrite
make[7]: *** [MapiClient] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
The user's tools versions:
automake 1.9.3
aclocal 1.9.3
autoconf 2.59
libtool ? (there is no --version: default Apple distribution one)
Here find attached the config.status file of the OSX compilation issue.
about the mailing list settings stuff (which should be off the list,
IMHO): there is a weird distinction between what developers think is
useful and what users think is useful. For the sourceforge/Mailman case
it seems to me that the former one is considered instead of the latter,
which is -- if you expect users to use it -- a wrong assumption. Since
SF is made for developers (you have to have a developers account for
instance), SF is clearly NOT the place for user interaction. Proof of
this theorem can be found in many projects that host a forum like
structure on their main website, that often allows guest posting, which
is clearly geared towards user usability.
(how big do you want to have the barrier that prevents someone from
reporting a problem today?)
Hi,
I downloaded and installed version 4.6 and am adapting some SQL scripts to
the preferred syntax from MonetDB.
However, I cannot find any document about what features are implemented, and
what is not yet ready.
for example, the "if exists" clause, using when dropping a table seems not
to be supported.
Is any documentation available on the supported syntax, datatypes etc?
Thanks,
Regards,
Dolf Smits
Dolf Smits
Senior Consultant Meta Directory Solutions
Siemens Nederland N.V.
Siemens Business Services
Bezoekadres
Prinses Beatrixlaan 26
Den Haag
Correspondentieadres
Postbus 16068
NL-2500 BB Den Haag
070 333 3654
070 333 2511
06 55844837
Dolf.Smits(a)siemens.com
www.siemens.nl
Deze e-mail is uitsluitend bedoeld voor kennisneming door de
geadresseerde(n), en mag niet aan anderen worden doorgestuurd of op andere
wijze ter kennis worden gebracht. Indien u niet de geadresseerde bent,
verzoek ik u om de afzender te waarschuwen en de e-mail direct te
verwijderen/vernietigen. De afzender wijst elke aansprakelijkheid voor (de
inhoud van) deze e-mail af.
