Thank for taking time to answer. Appreciated.
You basically confirmed my understanding: I need to go for a DIU
approach if I want table partitioning.
On 05-Dec-17 17:30, Bryan Pendleton wrote:
You are correct, Derby does not provide table partitioning features
such as those provided by Oracl
You are correct, Derby does not provide table partitioning features
such as those provided by Oracle.
And you are correct, a single Derby table is a single .dat file.
But modern filesystems handle very large files without problems. Is
there a particular reason that you think a very large file wil
I guess the question is if Apache Derby supports table partitioning (the
term used in Oracle RDBMS). I understand it doesn't.
This means that if I have an incredible large Derby table then that will
mean an incredible large single .dat file too. (a table is always stored
in a single .dat fi
We've seen .dat files in seg0 directory grow to several hundreds of
gigabytes. While everything works ok such a file becomes unmanageable
from an OS point of view. Is there a way to control when Derby starts a
new conglomerate? ... so that there are more .dat files but each of
them of less
