Tim,
In fact, MonetDB is kind of unique in the sense that it *never* does tuple
reconstruction. The low-level APIs tgat receive the result if a query get back
tables, which are still represented as BATs (arrays in which values belonging
to the same tuple are located at the same position).
Othe
> [I prefer to keep the mailing list involved to share the discussion;
> I hope you don't mind ... ;-) ]
Oops, I didn't notice...
> http://repository.cwi.nl/search/searchrepository.php?stheme=INS1),
> in particular
> http://repository.cwi.nl/search/fullrecord.php?publnr=14290
> http://repositor
Hi Tim,
[I prefer to keep the mailing list involved to share the discussion;
I hope you don't mind ... ;-) ]
On Mon, Jul 04, 2011 at 07:30:36PM +0200, Tim Speier wrote:
> Hello Stefan,
>
> thanks for your fast reply.
>
> I am especially interested in tuple reconstruction mechanisms in
> column
Hi Tim,
thanks for you interest in MonetDB.
In general, the recommend way to use MonetDB is via SQL, i.e., staying in
the standard multi-column relational world. Then, MonetDB (in particular
its SQL front-end) will automatically and transparently take care of using
the most efficient internal al
Dear all,
I'm trying to understand the tuple reconstruction algorithm in MonetDB.
Maybe someone can give me a short overview to understand it or the
place in documentation where I can do some research.
As far as I understood, the BAT consists of object-ids and values. Is
the object-identifier the
