Re: 3 questions...

Seems to me like it would be easier to just recompile Metakit with 
large file support enabled. But maybe Metakit is using internal 
structures that would be difficult to alter.

I'd like to know if that's the case. It would mean it's unlikely 
Metakit will support large files anytime soon. On the other hand, if 
large files were to materialize soon, it would be worth while just to 
wait.

Brian

On Aug 9, 2005, at 11:30 AM, Brian Kelley wrote:

> This is probably a non solution, but I once had a wrapper for 
> multi-file tables.
>
> I.e.
>
> vw = CombinedView(viewname, file1, file2, file3)
>
> and had python do all the internals, it was ok for read only
> structures but when tables got altered, ouch!
>
> It was essentially a "block" that used several metakit databases.  I
> also kept external index tags for quicker indexing.  I.e. I had
> metadata for ordered columns to quickly see which file had the
> specified column.
>
> One really interesting thing about metakit is that you can do joins on
> databases that are stored in seperate files!  This won't help you
> much, since you still have a total 2GB limit I think.
>
> Brian
>
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit