Licensing

[Jean-Pierre A. Radley]

Mark Luljak propounded (on Sat, Jun 28, 2014 at 08:24:00PM -0400):
| I see much talk of expanding the key files.
| 
| Nowhere am I seeing the index files being mentioned.  Is it possible to use
| extents and have an index grow to larger than 2GB, thus preventing the full
| size of extent key files from being used?
| 
| (Sort of like having `df` report disk full and being unable to write more
| files to disk, not because you're out of space, but because you're out of
| inodes.  If you don't hit one limit, might you not hit the other?)

A cursory look at some large filePro databases shows no index with a
size as much as 10% of the combined size of key+data. So even with the
maximum number of key and data extents, all near 2 GB, that would be
16 GB's worth of fields, and even as much as 12.4% of that for any one
index still falls below a 2 GB file limit.

Can you build an index so large that it exceeds the size of key+data?
I have done so, but cannot imagine it having any practical or useful
purpose.

-- 
JP