🚀 go-pugleaf

In article <5h754j$up@client3.news.psi.net>,
os2@mistik.express.net (Mustafa Soysal MS57) wrote:
|
|Yet the API limit is 2GB.....It was a recent problem a user could not
|get around.

That is the API limit for the offset in one seek call. The API limit
for how much you can read or write in one call is 4GB, but since
that is more than the memory limit it is purely academical. 

An experienced programmer will not have any problems working with
arbitrarily large collections of data. It is only a question of
selecting the appropriate tools. Checking my documentation, I discovered
that there is, indeed, a 64GB limit to the size of a single file.
With DB2, this means that you cannot have simultanously more than
4096TB in each database, for a total of some 1000000TB for each instance
of DB/2 you have running. No more than 256000 applications can 
simultaneously use your databases, and no more than 16384000 users
can have simultaneous access. Even so, I think hardware will be the
limiting factor for the forseeable future.