[ http://issues.apache.org/jira/browse/DERBY-1297?page=all ]
Mike Matrigali updated DERBY-1297: ---------------------------------- I do worry what adding a feature like this will do for the derby goal of a "zero admin database". I would hope that adding this feature would be done as an option to the user, where we could still package a default version of the system which would not require any admin interaction for "disk quota" like features. This seems to be the approach for file systems also, where disk quota is often available but not enabled by default. > implement a derby specific "disk quota" on the data stored the database. > ------------------------------------------------------------------------- > > Key: DERBY-1297 > URL: http://issues.apache.org/jira/browse/DERBY-1297 > Project: Derby > Type: New Feature > Reporter: Mike Matrigali > Priority: Minor > > Implement some way for users to indicate the amount of disk space in a > specific segment of the database. Current derby data files in one database > can only reside in a single segment, but it would be good to consider > implementation of the storage module which could allow data across multiple > segments. In the current implementation Derby just uses the space available > in the current seg0 directory until an allocation fails, subsquent attempts > to grow the database result in errors for the associate insert or update > statement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
